cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] [Commented] (CXF-3653) Bad URLs on generated service list page
Date Tue, 26 Jul 2011 17:21:09 GMT


Sergey Beryozkin commented on CXF-3653:

Hi Donal,

I'm afraid it's a non-fix issue.
I've finally managed to reproduce it with wget only. As I said, when I go to the services
page via Tomcat Manager, the services page does contain %2D, but the links are well-formed.

When I deploy a wepapp like "the-server-2" then I think the expectations are that URIs will
contain 'the-server-2'.
Tomcat does route the requests with "the%2Dserver%2D2" as confirmed by using wget - however
UrlEncoder does not encode '-' so we can't even do
a last resort processing in case of mismatches between "the-server-2" and "the%2Dserver%2D2".

I believe it's a non-fix one   

> Bad URLs on generated service list page
> ---------------------------------------
>                 Key: CXF-3653
>                 URL:
>             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:
> {code}
> (Well, that would actually be {{}},
but the point is that those two samples are from the same page, just loaded with differently-encoded
> 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:


View raw message