[prev in list] [next in list] [prev in thread] [next in thread] 

List:       shibboleth-dev
Subject:    Re: Attributes not appearing in .Net Request.Headers collection
From:       "Cantor, Scott" <cantor.2 () osu ! edu>
Date:       2015-06-10 17:38:19
Message-ID: B6C30E76-7CEE-4C5F-BC13-26DC5859A890 () osu ! edu
[Download RAW message or body]

On 6/10/15, 1:34 PM, "dev on behalf of Martin Robinson" <dev-bounces@shibboleth.net \
on behalf of martin.robinson@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 '&#246;' (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

-- 
To unsubscribe from this list send an email to dev-unsubscribe@shibboleth.net


[prev in list] [next in list] [prev in thread] [next in thread]