Aha! Revisiting that, I see I still have an uncommitted patch to make
content types to process configurable. I think that was an issue you
originally raised? But compression is another issue.
Yep.
Hmmm?
If the backend sends compressed contents with no content-encoding,
doesn't that
On 12/15/2013 11:37 PM, Christophe JAILLET wrote:
Apparently Proxy ~ xx is equivalent to ProxyMatch xx
So, should we:
1) just leave it as it is.
2) remove this behavior, which has never been documented.
3) update doc.
My choice is 2) because
- it has never been documented,
On 18 Dec 2013, at 14:47, Thomas Eckert wrote:
No, yes and I tried but couldn't get it to work. Following your advice I went
along the lines of
Yes, I'd be trying something like that. You can insert inflate (and deflate)
unconditionally, as they will check the headers themselves and remove
*r1552227*
