Feature Request P3
Status Update
Comments
ma...@gmail.com <ma...@gmail.com> #2
Hello,
Thank you for reaching out to us!
This issue seems to be outside of the scope of Issue Tracker. This Issue Tracker is a forum for end users to report bugs
and request features
on Google Cloud products. Please go through
I recommend you to
For now, I'm going to close this thread which will no longer be monitored. In case you want to report a new issue, please do not hesitate to create a new Issue Tracker describing your issue.
Thank you!
gr...@google.com <gr...@google.com>
pd...@gmail.com <pd...@gmail.com> #3
It works with Feedfetcher-Google now, but not Apple-PubSub. Please fix this. My feed is very compressible, so Mac users are stealing lots of bandwidth.
I'd just switch to Feedburner to avoid this altogether, but unfortunately Feedburner changes the feed and makes it incompatible with few clients.
I'd just switch to Feedburner to avoid this altogether, but unfortunately Feedburner changes the feed and makes it incompatible with few clients.
pd...@gmail.com <pd...@gmail.com> #4
PS. This isn't Urlfetch related.
rs...@gmail.com <rs...@gmail.com> #6
Note that issue 6011 is asking for the Feedburner user agent to be whitelisted (i.e. not a duplicate of this issue but an extension).
pv...@google.com <pv...@google.com> #7
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
Best regards, pvoutsinas
Best regards, pvoutsinas
Description
suggests that you maintain a white list of User-Agent:, Accept-Encoding: and Content-Type: headers.
I am writing Atom feeds (Content-Type: application/atom+xml) and I notice that neither of the clients (user-agent:) I'm using are getting compressed content.
Please can you add the following clients to your whitelist:
Apple-PubSub - Apple's Safari when in feed reader mode
Feedfetcher-Google - the client for Google Reader
I include a few lines from my access log to show what is happening.
These are just the two feed readers I've been using - it might be worth reviewing the capabilities of other feed readers too.
Thanks,
Chris.
As a control Camino (gecko based mac os x browser) gets a compressed copy...
[...] "GET /atom HTTP/1.1" 200 12775 - "Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en; rv:1.8.1.21) Gecko/20090327 Camino/1.6.7 (like Firefox/2.0.0.21pre),gzip(gfe)"
Google Reader gets uncompressed...
[...] "GET /atom HTTP/1.1" 200 73284 - "Feedfetcher-Google; (+
This is Safari first getting it as itself (compressed copy), realising that it's a feed so gets it again with its 'PubSub' hat on (uncompressed this time)...
[...] "GET /atom HTTP/1.1" 200 12775 - "Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_6; en-gb) AppleWebKit/525.27.1 (KHTML, like Gecko) Version/3.2.1 Safari/525.27.1,gzip(gfe)"
[...] "GET /atom HTTP/1.1" 200 73297 - "Apple-PubSub/65.1.2,gzip(gfe)"
Here are the snooped headers for Safari doing its double take...
GET /atom HTTP/1.1
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_6; en-gb) AppleWebKit/525.27.1 (KHTML, like Gecko) Version/3.2.1 Safari/525.27.1
Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language: en-gb
Accept-Encoding: gzip, deflate
Connection: keep-alive
Host:
HTTP/1.1 200 OK
Cache-Control: public
Content-Type: application/atom+xml; charset="utf-8"
ETag: "a87b433b93ed6eff414d4546dfbd1b35"
Content-Encoding: gzip
Date: Wed, 06 May 2009 11:41:24 GMT
Server: Google Frontend
Content-Length: 12634
GET /atom HTTP/1.1
User-Agent: Apple-PubSub/65.1.2
Accept: */*
Accept-Language: en-gb
Accept-Encoding: gzip, deflate
Connection: keep-alive
Host:
HTTP/1.1 200 OK
Cache-Control: public
Content-Type: application/atom+xml; charset="utf-8"
ETag: "a87b433b93ed6eff414d4546dfbd1b35"
Date: Wed, 06 May 2009 11:41:27 GMT
Server: Google Frontend
Transfer-Encoding: chunked