Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <52DE1E4A.6090609@t-online.de>
Date: Tue, 21 Jan 2014 08:14:18 +0100
From: Ewald Dieterich <ewald_dieterich@t-online.de>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64;
 rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: dev@httpd.apache.org
Subject: Re: Revisiting: xml2enc, mod_proxy_html and content compression
References: 
 <CAPV0b07QN3cEkus9GHXD3rbFiDYeinsAe2E4Q-DiR0n3PkcsGg@mail.gmail.com>
 <A020BE04-DDF8-4F62-9EDE-5A057093B798@webthing.com>
In-Reply-To: <A020BE04-DDF8-4F62-9EDE-5A057093B798@webthing.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

On 12/17/2013 12:47 PM, Nick Kew wrote:
>
> On 17 Dec 2013, at 10:32, Thomas Eckert wrote:
>
>> I've been over this with Nick before: mod_proxy_html uses mod_xml2enc to do the detection magic but mod_xml2enc fails to detect compressed content correctly. Hence a simple "ProxyHTMLEnable" fails when content compression is in place.
>
> 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.

I don't think you committed the patch to make content types 
configurable. Would you mind to share that patch? I have problems with a 
SharePoint 2013 server that sends a response with a multipart/related 
content type and I need to exclude that content type from processing:

Content-Type: multipart/related;
   type="application/xop+xml";
   boundary="urn:uuid:96f4525c-3b5b-4abf-ab09-7cfc8d346216";
   start="<6cccf4ee-894d-49c4-909e-c6b13dc4280a@tempuri.org>";
   start-Info="text/xml; charset=utf-8"

Ewald