Workdesk behind reverse proxy
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2014 06:17 PM
Hi guys
I installed Alfresco 5.0.a (custom install) and applied Workdesk to installation. I am also using nginx as reverse proxy that provides SSL. The access to /alfresco and /share and even online edit via Sharepoint integration behave as expected. However workdesk access over SSL does not work properly. Setup looks like this:
client –HTTPS–> nginx(server:443) –HTTP–> tomcat (server:8080)
<!–break–>
Although workdesk works fine when I access it via <em>http://server:8080/workdesk</em>, when I try to access it through reverse proxy I get garbled page, since the workdesk JSP pages are generating incorrect URLs (http://server/workdesk/ instead of being https://server/workdesk/).
Most of those URLs are generated from code like this
I guess that tomcat is not aware that I am accessing it through reverse proxy providing SSL. With properties <strong>alfresco.protocol</strong> and <strong>share.protocol</strong> set to <strong>https</strong>, this issue is avoided with /share and /alfresco access, however it is not the same with /workdesk.
Do you know how to change this?
I installed Alfresco 5.0.a (custom install) and applied Workdesk to installation. I am also using nginx as reverse proxy that provides SSL. The access to /alfresco and /share and even online edit via Sharepoint integration behave as expected. However workdesk access over SSL does not work properly. Setup looks like this:
client –HTTPS–> nginx(server:443) –HTTP–> tomcat (server:8080)
<!–break–>
Although workdesk works fine when I access it via <em>http://server:8080/workdesk</em>, when I try to access it through reverse proxy I get garbled page, since the workdesk JSP pages are generating incorrect URLs (http://server/workdesk/ instead of being https://server/workdesk/).
Most of those URLs are generated from code like this
<%=m_context.getBaseURL()%>
. However this code does not detect that I am accessing via SSL protocol on the reverse proxy.I guess that tomcat is not aware that I am accessing it through reverse proxy providing SSL. With properties <strong>alfresco.protocol</strong> and <strong>share.protocol</strong> set to <strong>https</strong>, this issue is avoided with /share and /alfresco access, however it is not the same with /workdesk.
Do you know how to change this?
Labels:
- Labels:
-
Archive
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-11-2014 03:42 AM
Hi mmrvelj,
For the case you are using Workdesk behind reverse proxy, there is additonal configuration in used owbootstrap.xml needed, so that <%=m_context.getBaseURL()%> can still be resolved. Search for the following commented section and uncomment it with your URLs:
Best regards,
deko
For the case you are using Workdesk behind reverse proxy, there is additonal configuration in used owbootstrap.xml needed, so that <%=m_context.getBaseURL()%> can still be resolved. Search for the following commented section and uncomment it with your URLs:
<!– ======================================================================Use this configuration option, if the application server is located behind a reverse proxyor a load balancer and the servername, port or application context path is different from what the actual client sees.=========================================================================== –> <!– <UrlOverwrite> <Server>http://servername</Server> <Base>http://servername/workdesk</Base> </UrlOverwrite> –>
Best regards,
deko