[
https://issues.apache.org/jira/browse/CXF-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064548#comment-13064548
]
Donal Fellows commented on CXF-3653:
------------------------------------
Well I get it consistently, but I only found it yesterday (when I got around to
upgrading). Arguably it's a bug in tomcat6 (specifically in the admin servlet)
that I get sent along encoded URLs in the first place, but that's really very
minor IMO; it shouldn't happen but it's hardly the end of the world. Moreover,
you can't stop people from putting weird stuff in URLs.
What's serious (and definitely a CXF issue) is that all that truncation is
happening; it didn't with the same codebase built against CXF 2.3.1 loaded into
the same version of Tomcat (though the URLs _were_ ugly, they worked). I can't
think why the URL would be getting chopped after 17 characters (and before the
adding of any suffixes) when {{%2D}} is present. A true WTF moment.
> 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
