[jira] [Issue Comment Edited] (CXF-3653) Bad URLs on generated service list page

["Sergey Beryozkin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CXF-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071320#comment-13071320 ] 

Sergey Beryozkin edited comment on CXF-3653 at 7/26/11 7:59 PM:
----------------------------------------------------------------

thanks Donal; we'd need to write a fairly specific code to do with parsing the base path and figuring out candidate chars which can be percent-encoded, given that the usual path encoder won't encode it  because '-' is a valid path char and even URLEncoder does not touch it :-). Hope that most users won't hit this issue in the 1st place - but feel free to reopen this issue if it becomes a nuisance, we'll sort something out. 

      was (Author: sergey_beryozkin):
    thanks Donal; we'd need to write a fairly specific code to do with parsing the base path and figuring out candidate chars which can be %-encoded, given that the usual path encoder won't encode it as '-' is a valid path char and even URLEncoder does not touch it :-). Hope that most users won't hit this issue in the 1st place - but feel free to reopen this issue if it becomes a nuisance, we'll sort something out. 
  
> Bad URLs on generated service list page
> ---------------------------------------
>
>                 Key: CXF-3653
>                 URL: https://issues.apache.org/jira/browse/CXF-3653
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.3.5
>            Reporter: Donal Fellows
>
> Deploy a webapp using CXF inside a container on a context path including a {{-}} character, and then access the CXF-generated {{services}} page using a URL where the hyphen has been %-encoded ({{%2D}} — this is done by Tomcat 6 under some circumstances). The result is that URLs on that page have a substantial chunk of the host name removed! Access the page with a URL that doesn't have any %-encoding and it all works.
> For example, in a deployment I have, I get:
> {code}
> Endpoint address: http://eric.rcs./soap
> {code}
> instead of the correct:
> {code}
> Endpoint address: http://eric.rcs.manchester.ac.uk:8080/taverna-server-2/soap
> {code}
> (Well, that would actually be {{http://eric.rcs.manchester.ac.uk:8080/taverna%2Dserver%2D2/soap}}, but the point is that those two samples are from the same page, just loaded with differently-encoded URLs.)
> This worked correctly in 2.3.1. I have both JAX-WS and JAX-RS services deployed, and I'm using Spring Security; I don't know if that's relevant.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira