Attributes not appearing in .Net Request.Headers collection

[Cantor, Scott]

On 6/10/15, 1:34 PM, "dev on behalf of Martin Robinson" <dev-bounces at shibboleth.net on behalf of martin.robinson at dai.co.uk> wrote:

>In fact, the missing attributes were really caused by the fact that the extra whitespace at the front of their values contained a line-feed! Hence, I guess the values appeared blank to IIS. But it would have been nice to at least have included the header name in the AllKeys array to tell me that it had a blank value. Grrrrrr!!!

Right, well, that definitely isn't allowed of course, since headers are separated by LFs.

>I actually tried adding 'ö' (an o-umlaut) into an attribute value in the SAML Response xml, and it correctly appeared as an Ö in the .Net headers collection. It would thus appear that .Net layer is properly decoding any UTF-8 before passing it to the application. So Non-ASCII characters appear to just work - but non-printable ones like line-feeds may not.

It's not the fact that it's non-printable, just that it's a significant character in HTTP.

-- Scott