Hello Volunteers,
I'd like to see if we can make progress on this one. Looking at the
latest comment in the JIRA, I see something from Greg on 2017-02-08.
GW> Note that when discussing encoding in terms of URIs there can be
GW> multiple encodings involved:
GW> + the encoding used to transport the URI itself (mostly specified by
GW> HTTP RFC's but some flexibility in implementation exists)
I looked at the HTTP/1.1 and 2.0 RFCS and the URI RFC and didn't see any
text about this. Can you please say more about what you mean here?
GW> + the encoding used for any encoded characters in the URI
As far as I know, the only encoding here is the "Percent encoding" which
isn't a character encoding of course.
GW> + the encoding of a HTTP URI path may sometimes differ from the URI
GW> of the query string
How would this difference be indicated?
Regardless of the answers to the above questions, I suggest we simplify
this and do not support configuring different encodings for the
different parts of the request: path, query string, and body. I propose
we implement this suggestion as follows.
* Modify request-character-encoding element in
javaee8/src/web-app_4_0.xsds to be:
<xsd:element name="request-character-encoding" type="javaee:string">
<xsd:annotation>
<xsd:documentation>
When specified, this element provides a default request
character encoding of the web application. This request
character encoding value pertains to all aspects of reading
octets from the request, including but not limited to, the
URI path, the query string, and any request body content.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
* Add the "This request character encoding value pertains to all..."
statement to ServletRequest.getCharacterEncoding(), at the end of the
first javadoc paragraph.
* In Frame section 3.12 Request data encoding, after the sentence "is
available on the ServletRequest interface," add the "This request
character encoding value pertains to all..." statement.
ACTION: Please reply by close of business Tuesday 4 April 2017.
Thanks,
Ed
--
| edward.burns_at_oracle.com | office: +1 407 458 0017
| 17 business days until planned start of Servlet 4.0 Public Review