On Friday 22 October 2010, Andrew Pimlott wrote: > It gets weirder: if I change text/plain to text/html, the encoding > is not added. It seems that AddOutputFilterByType catches proxied > requests if text/plain appears in its list of mime types, as if > all proxied requests were considered text/plain.
Do you have DefaultType text/plain set somewhere? If yes, try to not set that for the reverse proxied requests. I could imaging (but have not checked) that the processing order is like this: - DefaultType sets the content type - AddOutputFilterByType looks at the content type - mod_proxy sets the content type to what was received from the backend server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
