[wp-trac] [WordPress Trac] #22913: Files "corrupted" when streamed to file via HTTP API

[WordPress Trac]

#22913: Files "corrupted" when streamed to file via HTTP API
--------------------------+-----------------------------
 Reporter:  samthorne     |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  HTTP          |     Version:  3.2
 Severity:  normal        |  Resolution:
 Keywords:                |
--------------------------+-----------------------------

Comment (by dd32):

 > I've found that the best way to opt for no encoding is to simply not
 include the header. Setting Accept-Encoding: identity can confuse some
 servers, and q=0 is simply ignored by some servers.

 The edge case I was primarily worried about were servers that go "Oh, No
 Accept-Encoding? You must support industry standard deflate then surely?"
 - I hope this edge case is less common than servers saying "Oh, you
 support identity? Ok, here's deflated content then!".

 I don't think we'll be able to 100% support all edge cases without
 reimplementing a lot of things.. I'd be happy to go with not sending the
 header, that way, if a server assumes something, it's assumed wrong, it
 can't be argued it was just confused by a header it didn't understand :)

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/22913#comment:11>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software