Re: [CT-Guidelines LC] meta HTTP-Equiv ( LC-2013)

 Dear JOSE MANUEL CANTERA FONSECA ,

The Mobile Web Best Practices Working Group has reviewed the comments you
sent [1] on the Last Call Working Draft [2] of the Content Transformation
Guidelines 1.0 published on 1 Aug 2008. Thank you for having taken the time
to review the document and to send us comments!

The Working Group's response to your comment is included below, and has
been implemented in the new version of the document available at:
http://www.w3.org/TR/2009/WD-ct-guidelines-20091006/.

Please review it carefully and let us know by email at
public-bpwg-comments@w3.org if you agree with it or not before 6 November
2009. In case of disagreement, you are requested to provide a specific
solution for or a path to a consensus with the Working Group. If such a
consensus cannot be achieved, you will be given the opportunity to raise a
formal objection which will then be reviewed by the Director during the
transition of this document to the next stage in the W3C Recommendation
Track.

Thanks,

For the Mobile Web Best Practices Working Group,
Dominique Hazaël-Massieux
François Daoust
W3C Staff Contacts

 1.
http://www.w3.org/mid/93AA9E47B82F684A868C217766F48905374C6CCE40@EXCLU2K7.hi.inet
 2. http://www.w3.org/TR/2008/WD-ct-guidelines-20080801/


=====

Your comment on 4.3.1 Receipt of Cache-Control: no-transform:
> On section 4.3.6 it is mentioned the possibility of also checking the
> existence of meta HTTP-Equiv directives on the HTML response in addition
> to standard HTTP headers. However, this should be explicitly clarified
> and if so should apply to any server-generated header.
> 
> Proposed Amendment:
> 
> Clarify explictly if  proxies should check standard HTTP headers or
> meta HTTP-Equiv headers or both.
> 
> Best Regards


Working Group Resolution (LC-2013):
We agree. Section 4.2. Proxy Forwarding of Response to User Agent now
starts with a guideline that points out the equivalence between meta
element and the relevant HTTP header field when the relevant HTTP header
field is not present.

The updated text is available at:
http://www.w3.org/TR/2009/WD-ct-guidelines-20091006/Overview.html#sec-Proxy-Response

----

Received on Tuesday, 6 October 2009 15:34:27 UTC