[Using Sakai] is some one using sakai in a reverse proxy

[Sean Keesler]

I'd drop the /portal.

<VirtualHost *:80>
	ServerName sakai.mydomain.com
	ProxyPass         /  http://sakai.mydomain.com:8081/
	ProxyPassReverse  /  http://sakai.mydomain.com:8081/
        ProxyRequests Off
</VirtualHost>

This works for my setup fine.


Sean Keesler
130 Academy Street
Manlius, NY 13104
315-682-0830
sean.keesler at threecanoes.com





On Mon, Jul 12, 2010 at 2:15 PM, Tapas Mishra <mightydreams at gmail.com> wrote:
> On Mon, Jul 12, 2010 at 11:01 PM, Sean Keesler
> <sean.keesler at threecanoes.com> wrote:
>> I am using mod_proxy to simply run multiple tomcats (each with
>> different port numbers - 8080, 8081, 8082) on one box (for testing)
>> while still exposing only port 80 to the outside.  I am just passing
>> through the normal URL's and am not rewriting them, as you are trying
>> to do.
>
> I am not using any ReWriteRule I just dropped the binary of 2.7 in
> CATALINA_HOME and now I am trying this to be available to users on
> internet which will reach it via port 80
> when they type http://mydomain.com/sakai
>
> for this the Front end server which is physically different than where
> sakai is actually present
>
>
>
> Following ASCII Chart will explain my scenario
>
>                                                    |-------another
> server on lan where sakai is accessible as
> http://192.168.1.5:8080/portal
>                                                    |
> Server A--------------------------------------  |
> (Public IP)                                     |
>                                                    |
>                                                    |
>
>
> Now on Server A in above diagram
> in Apache vhost definition I have following
>
>
>
> ProxyPass /sakai http://192.168.1.5:8080/portal
> ProxyPassReverse /sakai http://192.168.1.5:8080/portal
>
>
> so that sakai on  http://192.168.1.5:8080/portal
>
> is served.
>
> Is this wrong ?
>
> I found that CSS and Javascripts are broken when users from internet
> are trying to reach with above configuration
> While on LAN there is no problem.
>
>
> I checked headers in client browser from internet
>
> When a user on internet types in browser http://mydomain.com/sakai
>
> I found some page elements generated urls as
>
> http://mydomain.com/library
>
> and not http://mydomain.com/sakai/path/to/css
>
> to which there is no ProxyPass on Server A so I asked as how many more
> URLs sakai applications is generating which are not starting from
> /portal and some thing else
>
> since if I include those in ProxyPass rules it is accessible .
> But I do not know how many more.
>
> There is no ReWriteRule and no change to any default configuration of sakai
> I do not want to increase my work.
>
> You can check this behaviour of sakai in the response via HTTP_LIVE an
> add on for firefox
> and see the Headers of response
>
>
> --
> Tapas
> _______________________________________________
> sakai-user mailing list
> sakai-user at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-user
>
> TO UNSUBSCRIBE: send email to sakai-user-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>
>