> On 9 Oct 2020, at 22:31, Ian Pilcher <arequipeno@xxxxxxxxx> wrote:
>
>
> Currently, the client (browser) sends its request with an Accept-
> Encoding header, but the proxy's request to the server does not include
> that header, so the server returns a 404.
That would appear to be a bug. Indeed, a regression since I did extensive testing
of the proxy and fixed a number of far-more-arcane bugs some years ago[1].
It seems implausible, and your test with curl seems to contradict it.
It also looks like questionable behaviour from the backend: if it's doing
content negotiation (as implied by it reacting to Accept-Encoding) then
this would seem to apply:
" If no Accept-Encoding field is present in a request [...]
Note: If the request does not include an Accept-Encoding field,
and if the "identity" content-coding is unavailable, then
content-codings commonly understood by HTTP/1.0 clients (i.e.,
"gzip" and "compress") are preferred; [...]"
[1] https://bz.apache.org/bugzilla/show_bug.cgi?id=43454 tracks a bunch of
them. Specifically those that weren't already fixed before I introduced it.
--
Nick Kew
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|