Hi mark!
thanks for the quick response.
I had previously found the passage from the specs that you
highlighted, but I interpreted it differently in that it says 'header
field' and did not specify value...but it sort of does right below
that plus this reference seals it for me:
HTTP/1.1 header field values can be folded onto multiple lines if the
continuation line begins with a space or horizontal tab. All linear
white space, including folding, has the same semantics as SP. A
recipient MAY replace any linear white space with a single SP before
interpreting the field value or forwarding the message downstream.
LWS = [CRLF] 1*( SP | HT )
from: http://www.w3.org/Protocols/rfc2616/rfc2616-sec2.html
Mark, I tried your suggestions and it didn't work. I stripped out all
sorts of stuff from the nginx config (this is nginx/0.6.34 btw),
including any proxy or header modifications, ssl, compression, etc,
and it still fails to recognize a multiline header value.
So at this point it sounds like a bug with nginx, but in the short
term mark would you be willing to remove the ', \n' and just leave it
as ', '? I did that in my local copy, so I should be all set, but
perhaps that will help others out?
I'm surprised this hasn't come up before. Still makes me wonder if
I'm missing anything, but that is looking less and less likely.
I'll go ahead and file a bug report with nginx. Thanks again Mark for
your help!
adam
On Feb 22, 4:01 pm, Marc Worrell <[email protected]> wrote:
> Hi Adam,
>
> On further investigation, could you try with a CRLF in the header?
>
> I see that in the code we use a "\n" and not "\r\n" as the http spec
> requires.
> Can you see if a "\r\n" makes nginx accept the header correctly?
>
> Thanks for your testing,
>
> - Marc Worrell
>
> On 23 feb 2009, at 00:54, Marc Worrell wrote:
>
>
>
> > Hi Adam,
>
> > The HTTP spec states clearly that header fields can be extended over
> > multiple lines.
> > Seehttp://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2
>
> > Quote from the first paragraph in section 4.2:
> >> Header fields can be extended over multiple lines by preceding each
> >> extra line with at least one SP or HT.
>
> > So when nginx doesn't pass the multi line authorization header field
> > correctly then I would assume it is a bug in nginx.
>
> > - Marc Worrell
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"OAuth" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/oauth?hl=en
-~----------~----~----~----~------~----~------~--~---
