http://bugs.winehq.org/show_bug.cgi?id=59573 --- Comment #5 from mata <sutupud@yahoo.com> --- (In reply to Hans Leidekker from comment #4)
Created attachment 80631 [details] patch
Thanks, here's a patch against current git wine that should fix this. The value 'utf-8' isn't actually valid for the Content-Encoding header (this server lives up to its name: TwistedWeb/12.2.0) but Windows accepts this and so should we.
Yes, thank you, the changes from that patch fix the issue. I guess validity would he hard to enforce for those headers, reading through rfc9110 they only "ought" to be registered with IANA, which in RFC terms is pretty weak language. And with registration would also be subject to change. Also, if the application wants to make use of a coding not supported by the transport layer (e.g. brotli or zstd), there's not really anything hindering it to set the "Accept-Encoding" header explicitly and then decompress it internally... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.