[
https://issues.apache.org/jira/browse/CAMEL-5458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421391#comment-13421391
]
Scott England-Sullivan commented on CAMEL-5458:
-----------------------------------------------
Hi Willem,
Can you point me to what is broken? Both the HTTP and Jetty component built
without error. The new unit test I supplied tested bridgeEndpoint with
matchOnUriPrefix set to true and false and URIs that contained a matched
context, mismatched context and ANY. The only one that is broken without the
patch is "ANY" where the consumer jetty endpoint is jetty:http://address:port
or jetty:http://address:port/. In both of these cases the incoming URI path is
appended regardless. This isn't the documented behavior nor expected behavior
given that it works with a context.
Also, is adding a new option to fix a broken behavior the right option?
Let me know what you found that is broken and I will take a further look.
Thanks,
Scott ES
http://fusesource.com
> Jetty/HTTP Pathless Consumer matchOnUriPrefix=true Breaks Producer
> bridgeEndpoint=true
> --------------------------------------------------------------------------------------
>
> Key: CAMEL-5458
> URL: https://issues.apache.org/jira/browse/CAMEL-5458
> Project: Camel
> Issue Type: Bug
> Components: camel-http, camel-jetty
> Affects Versions: 2.10.0
> Reporter: Scott England-Sullivan
> Assignee: Willem Jiang
> Attachments: CAMEL-5458.patch
>
>
> When a Jetty/HTTP endpoint that has the matchOnUriPrefix=true option set and
> is configured to match any URI (no path is specified) the HttpHelper
> concatenates the consumer path to the producer endpoint creating an
> HttpOperationUnsupportedException.
> For example the following will process as expected and the HttpHelper class
> will create the http://localhost:10021/proxy/ping consumer URI:
> {code}
> from("jetty:http://localhost:10020/ping?matchOnUriPrefix=true";)
> .to("jetty:http://localhost:10021/proxy/ping?bridgeEndpoint=true";);
> {code}
> While this code will create http://localhost:10021/proxy/ping/ping and create
> the exception (the only difference is there isn't a path on the consumer):
> {code}
> from("jetty:http://localhost:10020?matchOnUriPrefix=true";)
> .to("jetty:http://localhost:10021/proxy/ping?bridgeEndpoint=true";);
> {code}
> Test case and patch will be uploaded shortly.
> Thanks,
> Scott ES
> http://fusesource.com
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
