RE: [ACTION-634] CT guidelines and WAP1 gateways

Er, yes, sorry to be confusing. Some do, and quite a few don't.

Jo



> -----Original Message-----
> From: Francois Daoust [mailto:fd@w3.org]
> Sent: 04 February 2008 12:16
> To: Jo Rabin
> Cc: public-bpwg-ct
> Subject: Re: [ACTION-634] CT guidelines and WAP1 gateways
> 
> Oops. Actually, I thought you had said that quite a few WAP1 gateways DO
> obey the directive. No need to be that affirmative then. And no need to
> put that as a huge warning sign.
> 
> François.
> 
> Jo Rabin wrote:
> > Experience from the field seems to indicate that quite a few WAP1
> gateways don't actually obey the no-transform directive ... so we could
> water it down a bit and say that there is the possibility of mis-
> operation.
> >
> > Jo
> >
> >
> >
> >> -----Original Message-----
> >> From: public-bpwg-ct-request@w3.org [mailto:public-bpwg-ct-
> request@w3.org]
> >> On Behalf Of Francois Daoust
> >> Sent: 04 February 2008 11:03
> >> To: public-bpwg-ct
> >> Subject: [ACTION-634] CT guidelines and WAP1 gateways
> >>
> >>
> >> Per ACTION-634, I'm supposed to write a note to include in our
> >> guidelines to warn the readers that most of the guidelines are not
> >> compatible with WAP1 gateways as they would fail to transform WML to
> >> WMLC when they encounter a HTTP Cache-Control: no-transform header.
> >>
> >> Here is my proposal:
> >>
> >> -----
> >> Warning: Incompatibility with WAP1 gateways
> >>
> >> This document recommends the use of the Cache-Control: no-transform
> HTTP
> >> header by the origin server, with a view to controlling the content
> >> transformation proxy and in particular to preventing any kind of
> content
> >> transformation.
> >>
> >> The Cache-Control: no-transform directive applies to all the
> >> intermediaries between the origin server and the user agent. In
> >> particular, WAP1 gateways would obey the directive and would fail to
> >> compile WML into WMLC. Failure to do so would break the content
> delivery
> >> to the user agent.
> >>
> >> As a consequence, these guidelines cannot be used to deliver content
> >> through WAP1 gateways.
> >> -----
> >>
> >> It could go in the "2.2 Objectives" section formatted as a note with a
> >> different background color. Or maybe at some other place, it certainly
> >> doesn't have to be the first thing readers see.
> >>
> >> François.
> >>
> >>
> >>
> >
> >

Received on Monday, 4 February 2008 12:28:19 UTC