On 31/08/2015 13:40, arjan tijms wrote:
> Hi,
>
> On Mon, Aug 31, 2015 at 1:01 PM, Mark Thomas <markt_at_apache.org> wrote:
>> 1. URI decoding
>> You can't define this per web application since the URI needs to decoded
>> before it is mapped to the web application. Therefore this has to be a
>> container wide setting which means this pretty much has to use container
>> specific configuration.
>> What we could do is make UTF-8 rather than ISO-8859-1 the default.
>
> In some cases it's quite common to only deploy a single application to
> a single server, so in those cases it may make sense to let the
> application set a container wide setting.
>
> There are a few precedents (more or less) in Java EE for this today,
> like an application being able to define global resources
> (java:global).
I'm still not entirely comfortable with this. How would we resolve
conflicts?
For request URI I think a change of the default to UTF-8 with container
specific ways to change the default would be sufficient.
> Just to make sure, this is about the following container specific
> settings, right?
>
> Tomcat <Context URIencoding> in context.xml
Nope. <Connector URIEncoding="..." ... /> in server.xml
> GlassFish <parameter-encoding> in glassfish-web.xml
> JBoss EAP 6 <property name="org.apache.catalina.connector.URI_ENCODING">
> JBoss EAP 7 <servlet-container default-encoding>
I don't know about any of these.
Cheers,
Mark