[
https://issues.apache.org/jira/browse/CMIS-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204497#comment-13204497
]
Jens Hübel commented on CMIS-500:
---------------------------------
Are we really sure that the best answer to this problem is to handle this on
application level? I can't believe that zillions of Java web applications have
to deal with how to work behind a proxy. What happens with other webapps on the
same server?
Aren't there more generic solutions available to this issue, something like
http://tomcat.apache.org/tomcat-6.0-doc/api/org/apache/catalina/valves/RemoteIpValve.html.
I only want to keep our stuff simple, if possible.
> AtomPubUtils: Take the X-Forwarded-Host and X-Forwarded-Proto request headers
> into account when calculating the baseUrl
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: CMIS-500
> URL: https://issues.apache.org/jira/browse/CMIS-500
> Project: Chemistry
> Issue Type: Improvement
> Components: opencmis-server
> Affects Versions: OpenCMIS 0.7.0
> Reporter: Gert Dewit
> Assignee: Florian Müller
> Labels: patch
> Attachments: XForwardedHeaders.patch
>
>
> When the OpenCMIS server is deployed behind a reverse proxy, the service
> document doesn't return the correct URLs.
> If it takes the X-Forwarded-Host and X-Forwarded-Proto request headers into
> account when calculating the baseUrl the URLs are correct.
> A patch against revision 1241367 is attached.
--
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
