Yes, we are using long headers to send authorization back and forth between
clients and servers.
The client sends long "Authorization: ..." headers to the server (is there
a limit here?) and the server sends "X-Access-Token-Issued: ..:" headers to
the client (which will be limited, of course).
Is anyone from Google even watching this list?
On Jun 17, 1:36 pm, Michael wrote:
> Just bumping this - anyone at Google around to take a look at this
> bug? It's a little urgent still, I'm afraid.
>
> On Jun 9, 7:05 pm, Michael wrote:
>
>
>
>
>
>
>
> > Hello!
>
> > Issue 407 (http://code.googl
Just bumping this - anyone at Google around to take a look at this
bug? It's a little urgent still, I'm afraid.
On Jun 9, 7:05 pm, Michael wrote:
> Hello!
>
> Issue 407 (http://code.google.com/p/googleappengine/issues/detail?
> id=407) describes a bug from 2008 that drops all HTTP headers with a
Hi Will, good news is that we've fixed the bug in the mainline and the
fix will soon be deployed to production. We will be increasing the
length limit of the Location header, which will fix your issue. The
length limit on the other response headers will remain, however. Do
let us know if this is p
Will Norris wrote:
> Further investigation revealed that all headers are being removed from
> the HTTP response if the total length of the header (name, colon,
> space, and value) exceeds 498 characters. Like I said, this is only
> happening on the production AppEngine, not when running from
> lo
