[Using Sakai] running 10 lmses on a website can not get sakai behind a reverse proxy running

[Tapas Mishra]

On Thu, Feb 3, 2011 at 4:13 AM, Dunstall, Christopher
<CDunstall at csu.edu.au> wrote:
> Hi Tapas,
>
> I don't know httpd all that well, but some simple googling suggested to me a couple of things:
>
> 1. You have your conf file configured differently than every other how-to I found on reverse proxies... Take a look at [1].
>
> 2. What version of httpd are you using? There seems to be a bug [2] in mod_proxy/httpd prior to 2.2.4 that seems close to the symptoms you're getting.
>
> 3. Someone on the regular Sakai channels can correct me if I'm wrong, but default.sakai.properties needs to be renamed as sakai.properties (but that won't fix your problem I don't think).
>
> [1] http://www.apachetutor.org/admin/reverseproxies
> [2] https://issues.apache.org/bugzilla/show_bug.cgi?id=37770
>
> Hope that helps...
>
> Regards,
>
> Chris Dunstall | Service Support - Applications
> Technology Integration/OLE Virtual Team
> Division of Information Technology | Charles Sturt University | Bathurst, NSW
>
> Ph: 02 63384818 | Fax: 02 63384181
>
>
Hi Christopher thanks for the links.

I went through both.
How ever based on my observations here I found that we need some more
improvement in sakai doc
https://confluence.sakaiproject.org/display/~steve.swinsburg/Fronting+Tomcat+with+Apache+via+mod_proxy_ajp
for reverse proxy.
What I observed who so ever is using sakai is having a separate URL for sakai
i.e.
sakai.some_university.edu
and it is not that they are using it

as some_university.edu/something/sakai

which is what I have been trying till now.

What I found is if I add following

ProxyRequests Off
ProxyPreserveHost On

ProxyPass / http://192.168.1.4/
ProxyPassReverse / http://192.168.1.4/

ProxyPass /portal ajp://192.168.1.4:8009/portal
ProxyPassReverse /portal ajp://192.168.1.4:8009/portal

ProxyPass /library ajp://192.168.1.4:8009/library
ProxyPassReverse /library ajp://192.168.1.4:8009/library

then sakai is accessible on internet
but by looking at the headers if we test that then modify based on
individual page's response  then that will not be a good thing.

What ever application is generating the urls with /library is
basically doing at the root of site.

Now I have a new domain social.openitup.in to test this sakai instance.

I am able to get to the Tomcat home page but I sakai is still not reachable.

apache configuration for this is (we are using mod_proxy_ajp)

<VirtualHost *:80 >

ServerName social.openitup.in
ServerAdmin webmaster at localhost
ServerName social.openitup.in

ProxyRequests off
<Proxy *>
Order deny,allow
Allow from all
</Proxy>
ProxyPass / ajp://192.168.1.4:8009
ProxyPassReverse / ajp://192.168.1.4:8009


</VirtualHost>


in the file sakai.properties I have following entry
serverUrl=http://localhost:80


server.xml
I have commented following

<!-- <Connector port="8080" maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" /> -->

and enabled following

<Connector port="8009"
enableLookups="false" redirectPort="8443" protocol="AJP/1.3" />
I think by now we have followed the instructions on doc
https://confluence.sakaiproject.org/display/~steve.swinsburg/Fronting+Tomcat+with+Apache+via+mod_proxy_ajp
correctly.

But some thing is still missing.Let me know what you think for this
new URL social.openitup.in for sakai.