W3C

Disposition of comments for the Mobile Web Best Practices Working Group

Single page view

In the table below, red is in the WG decision column indicates that the Working Group didn't agree with the comment, green indicates that a it agreed with it, and yellow reflects an in-between situation.

In the "Commentor reply" column, red indicates the commenter objected to the WG resolution, green indicates approval, and yellow means the commenter didn't respond to the request for feedback.

CommentorCommentWorking Group decisionCommentor reply
LC-2377 Anne van Kesteren <annevk@opera.com> (archived comment)
Hey,

I don't really have any comments on 4.1.2 and 4.1.3. They seem fine, apart
from these nits:

1. The reference to XMLHttpRequest is out of date (the draft also had a
small name change).
2. XMLHttpRequest is not consistently marked up in the draft. I suggest
you simply use it as a name and not use <code> (unless you actually
reference the object and not the concept).
3. The time it is present in code XML is not completely in uppercase. That
is wrong.

Cheers,
Thanks, fixed in the latest revision of the spec. tocheck
LC-2378 Eduardo Casais <casays@yahoo.com> (archived comment)
Section 4.1.5.5 states the following:

"When forwarding an HTTP request with altered HTTP header fields, in addition
to complying with the rules of normal HTTP operation, proxies must include in
the request additional fields of the form "X-Device-"<original header name>
whose values are verbatim copies of the corresponding unaltered header field
values, so that it is possible to reconstruct the original header field values."

The intent of the statement is that the specific way of naming the backup fields
and the fact that their values are the original, unaltered ones sent by the device
are, together, the indispensable elements serving to restore the original HTTP
header fields.

The construction of the sentence should fully reflect this intent. I suggest
modifying it thus:

"[...], so that it is possible to reconstruct the original header fields."

This makes it clear that the conventions adopted enable servers to reconstruct
the entire HTTP header fields (names and values), not just their values.


E.Casais
The group agrees and has integrated the proposed change in the specification. tocheck

Developed and maintained by Dominique Hazaël-Massieux (dom@w3.org).
$Id: index.html,v 1.1 2017/08/11 06:43:26 dom Exp $
Please send bug reports and request for enhancements to w3t-sys.org