On 6 Dec 2003, at 01:22, Alain Javier Guarnieri del Gesu wrote:
* Tony Collen <[EMAIL PROTECTED]> [2003-12-04 15:56]:
Pier Fumagalli wrote:
On 4 Dec 2003, at 00:57, Tony Collen wrote:
It's easy: for each vhost, create whatever subsitemaps you want in Cocoon, then in each vhost config in httpd.conf, do something like:
------------------------------- <VirtualHost 111.222.333.444> ServerName example.com ServerAlias www.example.com ServerAdmin [EMAIL PROTECTED] DocumentRoot /usr/local/vhosts/example.com
ProxyPass /static/ ! ProxyPass / http://localhost:8888/cocoon/example/ ProxyPassReverse / http://localhost:8888/cocoon/example/ </VirtualHost> -------------------------------
I'm using this on openWeather.com and it works perfectly. My dream is to have all of my virtualhosts hosted this way, but that might never happen :^)
Are you sure that cookie-based sessions will actually work? :-)
Hmm, not sure. Perhaps I should have said, "it works for what I need"..
Who needs cookies anyway? :)
Cookies will work. So will SSL.
No they won't when those are created by sessions. The servlet Container will set a cookie for the "/cocoon/" path... Since the web application is proxied to "/" instead of "/cocoon/" the browser WILL NOT pass back the session ID to the server...
Pardon my ignorance, but doesn't that mean you can't use flow with such a system?
Geoff
