cancel
Showing results for 
Search instead for 
Did you mean: 

HTTPS/Squid reverse proxy

edk
Champ in-the-making
Champ in-the-making
I have read some of the older posts, but I am still unable to properly setup the following scenario:

All https connections are handled by a squid process acting as a reverse proxy. We have many applications being tested on a single external hostname, and all are redirected based on url regular expression matching.

Connecting to the Alfresco server running under tomcat is not the problem. The problem, is that Alfresco redirects traffic to unencrypted http - not https. This problem is exaggerated by Share, there are many redirects after login, all of which work after manually changing the URL from 'http' to 'https'.

I have edited the file: ./tomcat/webapps/share/WEB-INF/classes/alfresco/webscript-framework-config.xml
to include the following:

   <config evaluator="string-compare" condition="Server">
      <server>
         <scheme>https</scheme>
         <hostname>{DNS HOSTNAME}</hostname>
         <path>/share</path>
      </server>
   </config>
where {DNS HOSTNAME} is the fully qualified hostname.

…as directed by this page: http://wiki.alfresco.com/wiki/Web_Scripts_Framework#Web_Server_Host

What else should I be doing?
4 REPLIES 4

edk
Champ in-the-making
Champ in-the-making
This morning I have updated the Alfresco and Share war files to build 1526. There is no change in the behavior.

Currently, the configuration looks like:

alfresco/WEB-INF/classes/alfresco/webscript-framework-config.xml:
   <config evaluator="string-compare" condition="Server">
      <server>
         <scheme>https</scheme>
         <hostname>{DNS NAME}</hostname>
      </server>
   </config>

share/WEB-INF/classes/alfresco/webscript-framework-config.xml:
   <config evaluator="string-compare" condition="Server">
      <server>
         <scheme>https</scheme>
         <hostname>{DNS NAME}</hostname>
      </server>
   </config>

p.s. tomcat v5.5.23, jre v1.6.11

edk
Champ in-the-making
Champ in-the-making
This issue has been resoved… After adding these lines:
                proxyName="{DNS NAME}"
                scheme="https"
                proxyPort="443"
to the Connector entry in ./tomcat/conf/server.xml

See this page for more background:

http://tomcat.apache.org/tomcat-5.5-doc/proxy-howto.html

mrojas73
Champ in-the-making
Champ in-the-making
This issue has been resoved… After adding these lines:
                proxyName="{DNS NAME}"
                scheme="https"
                proxyPort="443"
to the Connector entry in ./tomcat/conf/server.xml

See this page for more background:

http://tomcat.apache.org/tomcat-5.5-doc/proxy-howto.html

Where did you add them to?

edk
Champ in-the-making
Champ in-the-making
Sorry for the long delay, but this may help someone else out too.

The lines where added to the file tomcat/conf/server.xml in the following XML record:

<!– Define a non-SSL HTTP/1.1 Connector on port 8080 –>
<Connector port="8080" URIEncoding="UTF-8" maxHttpHeaderSize="8192"  …