Just make up your own X-... header - that will make it though - because nobody will know what it does, they wont touch it.
The ones that are cleaned up are the ones with defined meanings. On Tue, Jan 3, 2012 at 1:59 PM, objectuser <[email protected]> wrote: > I would like to set an HTTP header on some of my requests in order to > filter the requests properly. > > Looking at the docs, there is a section on Request Headers that states is > part: > > An incoming HTTP request includes the HTTP headers sent by the client. For > security purposes, some headers are sanitized or amended by intermediate > proxies before they reach the application. > > > This leads me to believe that there should be some headers that I might be > able to use that are not filtered. I'm wondering if there is a list of > headers anywhere that I might be able to browse through and potentially > repurpose. Based on another discussion in this group, I tried > X-Forwarded-For, > but that doesn't seem to make it through on the server (and since I've > tried a variety of others with no luck). > > Thanks for any help. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/5yh9ECHYBRkJ. > 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/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
