W3C home > Mailing lists > Public > public-wsc-wg@w3.org > June 2008

Re: Redirection Chains

From: Thomas Roessler <tlr@w3.org>
Date: Wed, 11 Jun 2008 16:41:18 +0200
To: Mary Ellen Zurko/Westford/IBM <Mary_Ellen_Zurko@notesdev.ibm.com>
Cc: johnath@mozilla.com, public-wsc-wg@w3.org
Message-ID: <20080611144118.GF272@iCoaster.does-not-exist.org>

On 2008-06-11 10:29:02 -0400, Mary Ellen Zurko/Westford/IBM wrote:

> > >Note that this applies whether or not the resource in which the
> > >non-interactive chain of
> > >
> > >    * redirections terminates is TLS protected in any manner. In
> > >    particular, even if the retrieval of the final resource in the
> > >    chain of redirections is strongly TLS protected, clients MUST
> > >    signal an error. Also note that this section is not limited to
> > >    HTTP level redirection mechanisms; it also covers redirections
> > >    that are caused by scripting or HTML constructs. 
> > > 
> > >This section is confusing since it suggests that we are signalling
> > >an error, not a warning as mentioned above. It's also not clear how
> > >to interpret this text in light of things like image transfers
> > >which, if they occurred over unprotected connections would be cause
> > >for mixed mode treatment, but not warnings or errors. I can't
> > >declare conformance here at the moment, given these confusions.
> > 
> > http://www.w3.org/2006/WSC/wiki/Firefox_3.0_Conformance_with_June_LC
> > 
> > The "signal an error" language is old, and preceded the introduction
> > of the different error signalling levels, if I recall correctly.

> Do we have an action tracking fixing this language? 

No, since we don't know what the fix is, yet.

-- 
Thomas Roessler, W3C  <tlr@w3.org>
Received on Wednesday, 11 June 2008 14:41:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 11 June 2008 14:41:55 GMT