[ https://issues.apache.org/jira/browse/DELTASPIKE-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018091#comment-15018091 ]
Armin Schaberl commented on DELTASPIKE-1030: -------------------------------------------- after some research, i think it is a controversial issue. since the response character encoding was not set before, it defaults to 'ISO8859-1'. so parameters of the encoded redirection url are encoded in ISO8859-1. back on the server the server want's to decode it using UTF-8. my opinion is, that url parameters (especially on the same server) should not be encoded by the response's character set because the uri encoding could always be a different one. it is a valid ISO8859-1 encoded response with an url, whose parameter are (url) encoded in UTF-8. setting the default response encoding (for every page) within a servlet filter is possible, but may break some parts of our applications. it would be great if you could provide the possibility to configure the uri encoding for the initial redirect. in the meanwhile i copied and @Specialize-d the LazyWindowStrategy to fake the response character encoding, according to the system setting, directly before ClientWindowHelper.handleInitialRedirect gets called. > Initial redirect does not encode URL properly > --------------------------------------------- > > Key: DELTASPIKE-1030 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-1030 > Project: DeltaSpike > Issue Type: Bug > Components: JSF-Module > Affects Versions: 1.5.1 > Environment: JBoss EAP 6.4.4 > -Dorg.apache.catalina.connector.URI_ENCODING=UTF-8 > Reporter: Armin Schaberl > Assignee: Rafael Benevides > Fix For: 1.5.2 > > > Unicode Parameters on the initial request to an application won't get encoded > properly. > They are currently encoded by the response's default encoding (i.e. > ISO8859-1). The encoding for the servers URL parameters could possible be > another one. I.e. we are using a UTF-8 (due to vm parameter > -Dorg.apache.catalina.connector.URI_ENCODING=UTF-8 on our JBoss EAP 6.4). > So Deltaspike generates a redirect URL to the same Application/Server with an > incorrect encoding. > The test ist quite simple, just use parameters with German umlauts on the > initial request to a server which supports UTF-8 URL parameters. -- This message was sent by Atlassian JIRA (v6.3.4#6332)