cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CXF-5168) Impossible to pass '+' character as is as part of HTTP query with WebClient
Date Tue, 30 Jul 2013 13:47:49 GMT

     [ https://issues.apache.org/jira/browse/CXF-5168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sergey Beryozkin updated CXF-5168:
----------------------------------

    Description: 
URL Encoder encodes "\+" as "%2B" however this may affect the servers expecting '\+' as is,
in fact '+' is not a query reserved character.
What further complicates is that URL encoder will encode ' ' as '\+'.

The path encoding process manages it correctly, it will retain '\+' and will encode ' ' as
'%20'.

For query: we need to keep '\+' as is and if users want it as '%2B' they they can directly
use '%2B'. The same goes for ' ' - encoding it to '\+' has not been a problem so far but if
they need they can always use '%20'

  was:
URL Encoder encodes "+" as "%2B" however this may affect the servers expecting '+' as is,
in fact '+' is not a query reserved character.
What further complicates is that URL encoder will encode ' ' as '+'.

The path encoding process manages it correctly, it will retain '+' and will encode ' ' as
'%20'.

For query: we need to keep '+' as is and if users want it as '%2B' they they can directly
use '%2B'. The same goes for ' ' - encoding it to '+' has not been a problem so far but if
they need they can always use '%20'

    
> Impossible to pass '+' character as is as part of HTTP query with WebClient 
> ----------------------------------------------------------------------------
>
>                 Key: CXF-5168
>                 URL: https://issues.apache.org/jira/browse/CXF-5168
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>            Reporter: Sergey Beryozkin
>            Assignee: Sergey Beryozkin
>
> URL Encoder encodes "\+" as "%2B" however this may affect the servers expecting '\+'
as is, in fact '+' is not a query reserved character.
> What further complicates is that URL encoder will encode ' ' as '\+'.
> The path encoding process manages it correctly, it will retain '\+' and will encode '
' as '%20'.
> For query: we need to keep '\+' as is and if users want it as '%2B' they they can directly
use '%2B'. The same goes for ' ' - encoding it to '\+' has not been a problem so far but if
they need they can always use '%20'

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message