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. > See http://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 -~----------~----~----~----~------~----~------~--~---
