Closed yurykats closed 8 years ago
This prevents riofs from being used against a custom S3 storage provider, since the said provider implements stricter header checks, and rejects riofs's request with 400:
14:34:38 [con](http_connection_on_responce_cb http_connection.c:583) [con: 0x1b363a0] Server returned HTTP error: 400 (Bad Request). AWS message: Unsupported Accept-Encoding specified
Great finding, thank you!
Accept-Encoding header is set to “identify” in http_connection.c
This is a typo! It should be “identity”. (see https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html)