- From: <fd@w3.org>
- Date: Thu, 11 Feb 2010 22:32:02 +0000
- To: Mark Nottingham <mnot@mnot.net>
- Cc: public-bpwg-comments@w3.org,Francois Daoust <fd@w3.org>, public-bpwg-comments@w3.org
Dear Mark Nottingham , The Mobile Web Best Practices Working Group has reviewed the comments you sent [1] on the Last Call Working Draft [2] of the Guidelines for Web Content Transformation Proxies 1.0 published on 6 Oct 2009. 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/2010/WD-ct-guidelines-20100211/. Please review it carefully and let us know by email at public-bpwg-comments@w3.org if you agree with it or not before 11 March 2010. 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/5229FADA-66E7-432B-BD8F-581E83DD56B2@mnot.net 2. http://www.w3.org/TR/2009/WD-ct-guidelines-20091006/ ===== Your comment on 4.1.5.2 Avoiding "Request Unacceptable" Responses: > e.g. it allows retrying a POST request upon a 406, even though this > isn't allowed in HTTP. Working Group Resolution (LC-2327): We agree and have removed the exception to the rule in 4.1.5.2. The section now refers to section 9.1.1 of RFC2616. ---- Your comment on 4.2.3 Receipt of Cache-Control: no-transform: > It effectively allows proxies to ignore no-transform, if they really > want to. Working Group Resolution (LC-2328): We agree and have removed the exception to the rule in 4.2.3. The guidelines do not allow proxies to ignore no-transform anymore. ---- Your comment on 4.2.5 Server Rejection of HTTP Request: > It blurs the semantics of a 200 response based upon its content. Working Group Resolution (LC-2329): We take your point but pragmatically speaking the distinction is blurred by Web site owners. ----
Received on Thursday, 11 February 2010 22:32:05 UTC