[google-appengine] Re: User-Agent header is corrupt - Marzia Niccolai - com.googlegroups.google-appengine

7 messages in com.googlegroups.google-appengine[google-appengine] Re: User-Agent hea...

From	Sent On	Attachments
Vlajbert	25 May 2008 10:02
Ross Ridge	26 May 2008 01:42
Marzia Niccolai	27 May 2008 15:04
Vlajbert	27 May 2008 17:36
Ross Ridge	27 May 2008 17:48
Marzia Niccolai	27 May 2008 17:51
Ross Ridge	27 May 2008 18:01

Subject:	[google-appengine] Re: User-Agent header is corrupt
From:	Marzia Niccolai (mar...@google.com)
Date:	05/27/2008 03:04:54 PM
List:	com.googlegroups.google-appengine

Hi, Currently, you are not able to set the User-Agent header with Google App Engine.

For all applications, Google App Engine doesn't allow various headers to be set: ACCEPT_ENCODING

Outbound request headers: CONTENT_LENGTH, DATE, HOST, REFERER, USER_AGENT, VARY, VIA, X_FORWARDED_FOR

Response headers: CONTENT_ENCODING, CONTENT_LENGTH, DATE, SERVER, TRANSFER_ENCODING

Please feel free to file a feature request for User-Agent support.

-Marzia

On Mon, May 26, 2008 at 1:42 AM, Ross Ridge <rri...@csclub.uwaterloo.ca> wrote:

Vlajbert wrote:

Am I crazy here or not?

Something is corrupting the user-agent header. [...] Notice the ,gzip(gfe) at the end of the User-Agent. ... Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9) Gecko/ 2008051202 Firefox/3.0,gzip(gfe)

It's probably "Google Front End" that's corrupting the User-Agent header. I'm not sure why they felt the need to do this, or why they decided to do in away that generates an invalid User-Agent header, but it's something that shows up in server logs outside of Google.