GitHub user Dawuid opened a pull request:
https://github.com/apache/camel/pull/1201
Add publishedEndpointUrl capability to rsServer
Endpoint definition allows to specify publishedEndpointUrl, but this
attribute is not available in rsServer element. This attribute
(publishedEndpointUrl) is used by WadlGenerator to compose baseUri resource in
the WADL. If you are deploying a REST service in an internal net but exposed to
internet (through reverse proxy, for example) , WADL should inform such
publishing address (in a similar way that you can do it with WSDL in camel-cxf).
Actually, since no publishedEndpointUrl can be used in rsServer definition,
baseUri is built with HTTP request information. That means internal network
information could be leaked in a reverse proxy scenario.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Dawuid/camel patch-1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1201.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1201
----
commit 75140887ed9bbc02d5b6638a2e928deaa70c23a6
Author: David Santos <[email protected]>
Date: 2016-10-07T07:19:13Z
Add publishedEndpointUrl capability to rsServer
Endpoint definition allows to specify publishedEndpointUrl, but this
attribute is not available in rsServer element. This attribute
(publishedEndpointUrl) is used by WadlGenerator to compose baseUri resource in
the WADL. If you are deploying a REST service in an internal net but exposed to
internet (through reverse proxy, for example) , WADL should inform such
publishing address (in a similar way that you can do it with WSDL in camel-cxf).
Actually, since no publishedEndpointUrl can be used in rsServer definition,
baseUri is built with HTTP request information. That means internal network
information could be leaked in a reverse proxy scenario.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
