On Mon, Sep 9, 2013 at 10:58 PM, Jeff Lockhart <[email protected]> wrote:
> Although community support has moved to Stack > Overflow<https://groups.google.com/forum/#!topic/google-appengine/Z6XN_64cA7w>, > I find it difficult to receive any attention to my questions > there<http://stackoverflow.com/questions/18668370/crlf-changing-to-in-http-response-header>. > I have come across an issue where the CR+LF characters in my > WWW-Authenticate header are turned into underscores, messing up the syntax > of the header. Is there a proper way to put CR+LF into header strings other > than "\r\n"? > > I see that Barry has already responded to your SO post, so I'll keep this brief. HTTP headers are allowed to be quite long. Apache defaults to allowing 100 headers, with each header allowed to be 8,000+ bytes long ( http://httpd.apache.org/docs/2.2/mod/core.html#limitrequestline ). IIS and some enterprise-focused servers tend to allow even longer headers (header sizes are usually equal to the server's buffer size or similar constraint - not by RFC). In regards to the underscore issue, that's most likely App Engine being a bit overeager in sanitizing responses. Most likely this is a deliberate design decision and not a bug. If you really want an answer, it might be better to file an issue in the tracker: https://code.google.com/p/googleappengine/issues/list ----------------- -Vinny P Technology & Media Advisor Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
