Am 29.01.19 um 12:47 schrieb Tim Düsterhus:
> I initially implemented it as a `goto error`. That disables the actual
> compression of the body. Unfortunately the `Content-Encoding` header is
> already modified, thus the client expects gzip, but receives plain data.
> I could mitigate that by modifying the ETag header first which is the
> most likely one to fail.
> Ideally the http_set_comp_reshdr / htx_set_comp_reshdr functions run
> atomically, if one header fails to be modified all of the headers revert
> to their original values. But this is currently not the case.
> What do you think?

I just notice the `http_select_comp_reshdr` function. I guess I can put
the ETag validation there and only check for strong / weak in

Best regards
Tim Düsterhus

Reply via email to