[
https://issues.apache.org/jira/browse/CAMEL-5458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423095#comment-13423095
]
Scott England-Sullivan commented on CAMEL-5458:
-----------------------------------------------
Willem,
The documentation is:
*bridgeEndpoint* | *false* | If the option is true, then the Exchange.HTTP_URI
header is ignored, _*and use the endpoint's URI for request*_. You may also set
the throwExcpetionOnFailure to be false to let the AhcProducer send all the
fault response back.
There is nothing about appending the current path to the supplied endpoint. It
states that it will *use the endpoints URI*. So maybe the question is, which
endpoint is the documentation referring to?
Also, if you remove all the patches and run just my unit test, it will show you
several ways it breaks using the current logic.
Either way you look at it, the functionality is definitely broken on some level
and is not delivering on the documented intent.
I am not sure what the best way to handle that is but I think these questions
need to be answered first.
I appreciate your help and patients,
Best Regards,
Scott ES
> 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-v2.patch, CAMEL-5458-willem.patch,
> 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
