Switch to HTTP 1.1 for outgoing requests instead of HTTP 2. There are problems with Rabbit MQ REST API when using HTTP 2. It doesn't handle requests for protocol version upgrades correctly.
Fix headers of proxy requests. The modes json-proxy and xml-proxy modify answer, so passing headers Content-Encoding and Content-Length from the original response makes the response of the stub is invalid.
Disable decompressing of response for the mode proxy. Decompression without excluding the content-encoding header produces an incorrect response. Also, an expectation from the mode proxy is the response is returned without modification, but decompression breaks the expectation.
Up version of sttp client, because previous version wrong handles Content-Type and Content-Length headers if they are written in low-case. Some clients send these headers in low-case. Fix in sttp repository: https://github.com/softwaremill/sttp/pull/2135.
Switch to HTTP 1.1 for outgoing requests instead of HTTP 2. There are problems with Rabbit MQ REST API when using HTTP 2. It doesn't handle requests for protocol version upgrades correctly.
Fix headers of proxy requests. The modes json-proxy and xml-proxy modify answer, so passing headers Content-Encoding and Content-Length from the original response makes the response of the stub is invalid.
Disable decompressing of response for the mode proxy. Decompression without excluding the content-encoding header produces an incorrect response. Also, an expectation from the mode proxy is the response is returned without modification, but decompression breaks the expectation.
Up version of sttp client, because previous version wrong handles Content-Type and Content-Length headers if they are written in low-case. Some clients send these headers in low-case. Fix in sttp repository: https://github.com/softwaremill/sttp/pull/2135.
@mockingbird/maintainers