Re: no-transform & Warning2002-04-16 07:43:34Mark Nottingham wrote: These mechanisms are required in order to be HTTP-compliant; therefore, I'd say they should be part of the ICAP server's HTTP stack. Hm, this assumes that the payload (i.e. the content-path protocol) is NOT transparent to the OPES/Callout protocol, i.e. the OPES/Callout protocol needs to have knowledge about the sematics of the encapsulated application protocol (HTTP in this case). Do we want to make this assumption? Comments? -Markus
|
|