You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Donal Fellows (JIRA)" <ji...@apache.org> on 2011/07/13 12:58:00 UTC
[jira] [Created] (CXF-3653) Bad URLs on generated service list page
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
[jira] [Commented] (CXF-3653) Bad URLs on generated service list
page
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064578#comment-13064578 ]
Sergey Beryozkin commented on CXF-3653:
---------------------------------------
Looks like it :-)
As a workaround - you may want to try 'hiding' endpoints from the services page,
setting "org.apache.cxf.endpoint.private" true property may help,
> 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
[jira] [Resolved] (CXF-3653) Bad URLs on generated service list
page
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Beryozkin resolved CXF-3653.
-----------------------------------
Resolution: Won't Fix
Assignee: Sergey Beryozkin
Closing as won't fix for now - can be reopened if needed
> 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
> Assignee: Sergey Beryozkin
>
> 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
[jira] [Commented] (CXF-3653) Bad URLs on generated service list
page
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066749#comment-13066749 ]
Sergey Beryozkin commented on CXF-3653:
---------------------------------------
works with 2.4.1 & 2.3.5, Tomcat 6.0.29, when going via Manager servlet I'm seeing:
Available RESTful services:
Endpoint address: http://localhost:8080/the%2Dservices%2D2/personservice
WADL : http://localhost:8080/the%2Dservices%2D2/personservice?_wadl&type=xml
where the-services-2.war was originally deployed.
Can you try with "locahost:8080" only, instead of "eric.rcs.manchester.ac.uk:8080" ?
> 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
[jira] [Issue Comment Edited] (CXF-3653) Bad URLs on generated
service list page
Posted by "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
[jira] [Commented] (CXF-3653) Bad URLs on generated service list
page
Posted by "Donal Fellows (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CXF-3653) Bad URLs on generated service list
page
Posted by "Donal Fellows (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064480#comment-13064480 ]
Donal Fellows commented on CXF-3653:
------------------------------------
BTW, I will probably work around this so that it's not normally encountered by users of the site (i.e., so that it will require people to actually use the %-encoded URLs directly to see) but that's just a workaround for my deployment, not a fix at all.
And I make no guarantee about those URLs remaining up. :-)
> 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
[jira] [Commented] (CXF-3653) Bad URLs on generated service list
page
Posted by "Donal Fellows (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067078#comment-13067078 ]
Donal Fellows commented on CXF-3653:
------------------------------------
If I fetch {{http://localhost:8080/taverna%2Dserver%2D2/services}} using wget, I still get mangled addresses.
An example mangled address is: {{http://localhost/soap?wsdl}}
That's definitely wrong (where's the port? where's the webapp name?)
> 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
[jira] [Commented] (CXF-3653) Bad URLs on generated service list
page
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071234#comment-13071234 ]
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: 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
[jira] [Commented] (CXF-3653) Bad URLs on generated service list
page
Posted by "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 commented on CXF-3653:
---------------------------------------
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
[jira] [Commented] (CXF-3653) Bad URLs on generated service list
page
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066747#comment-13066747 ]
Sergey Beryozkin commented on CXF-3653:
---------------------------------------
If you could explain how to reproduce then it would help.
I dropped a sample webapp with a "-" into tomcat 6/webapp, services page was displayed correctly...
> 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
[jira] [Commented] (CXF-3653) Bad URLs on generated service list
page
Posted by "Donal Fellows (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071292#comment-13071292 ]
Donal Fellows commented on CXF-3653:
------------------------------------
It was the weird chopping of the URL that was the issue (given that it worked in previous versions). It's not a great problem though, as I can work around it easily enough (and have done) and my downstream users will probably use hyphen-less names.
I hate systems that add extra %-encoding for no good reason. Ho hum.
> 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
[jira] [Commented] (CXF-3653) Bad URLs on generated service list
page
Posted by "Donal Fellows (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064617#comment-13064617 ]
Donal Fellows commented on CXF-3653:
------------------------------------
I'm already using that property (I've got a REST service that's serving up the documentation, but it's not relevant to any “official” service offered) and as I said, I've a workaround; it's not critical to me to get this fixed.
> 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
[jira] [Commented] (CXF-3653) Bad URLs on generated service list
page
Posted by "Sergey Beryozkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064497#comment-13064497 ]
Sergey Beryozkin commented on CXF-3653:
---------------------------------------
Is it consistently reproducible with Tomcat 6 ?
Seems like a bug in CXF if it reports "taverner-server-2" as taverner%2Dserver%2D2...
> 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