[
https://issues.apache.org/jira/browse/DELTASPIKE-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018419#comment-15018419
]
Gerhard Petracek commented on DELTASPIKE-1030:
----------------------------------------------
[~aschaberl]
thx for providing more details about the constellation you have.
we could provide an optional UrlEncoder spi, because we have several parts
which encode an url (and we can't provide a config for all of them).
however, you should never mix encodings in your pages. if your application
would break because you mixed it, you need to fix your application (because
sooner or later it would break anyway due to that reason).
> 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)
