[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):

 > perhaps worth it digging up some clients that don't accept compressed
 content and seeing what they use.

 Good luck there..[[BR]]
 I'd rather be explicit rather than relying upon default behaviours, so by
 specifying the header with only identity, we're saying "We just want this,
 and we don't understand the rest".. specifying them as q=0 seems like it'd
 work around a buggy server here or there, but may be understood
 incorrectly by a HTTP/1.0 server.

 Worth noting, that WP_HTTP claims to be a HTTP/1.0 client, so if it's
 sending 1.1 headers, we should change the version to 1.1.[[BR]]
 I'd also be fine with dropping the "Quality" param completely from this
 lineup so it's HTTP/1.0 compatible, but that may mean HTTP/1.1 servers
 (all of them..) would choose compress or gzip over deflate, and face it,
 'deflate' is the ONLY code branch that has been tested with WP_HTTP, since
 every server supports it, the other branches are rarely hit.

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