Re: processing of ICAP Transfer-Ignore options

> I have a number of clients dealing with this most common case among the popular CMS systems today...
>
>
> GET http://example.com/index.php?some/file.jpg HTTP/1.1
> ...
> HTTP/1.1 200 Okay
> Content-Type: text/xml
> ...
> GET http://example.com/imagews/1861245634-230is86 HTTP/1.1
> ...
> HTTP/1.1 200 Okay
> Content-Type: image/jpeg
> ...
>
>
> If one is lucky the CMS *may* put .jpg on the second URI name.
>
> Amos

The referred clients use reverse proxy or forward proxy ?

Yeah, the more we talk about this issue, the more I think the existing Transfer-Ignore
and a new Ignore-Content-Type are bogus since there are still too many web servers
and CMS's that do things wrong. Both the "file extension" and the Content-Type is too
often wrong.

For RESPMOD, icapd uses content sniffing since when it blocks
an object it insists in sending new content with the correct Content-Type.

I came up with the original question since I try to optimize performance and
ignore irrelevant content by not sending it to the ICAP server.
I think we are stuck with processing all traffic without ignoring any content.

Marcus
Received on Mon Apr 16 2012 - 14:51:55 MDT