nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

multiple domains on a single lsds/lscs

System

We are planning to host different domains on a single lsds/lscs.

http://www.site1.com --> http://lsds:1776/site1/
http://www.site2.com --> http://lsds:1776/site2/

Has anyone been able to achieve this and how did you make it work?

Find more posts tagged with

Comments

nipper

That is trivial if you know how to use apache rewrites and virtual hosts.

Of course since you give no details of what you your environment is, that answer may or may not help.

Migrateduser

In just trying to configure one site, I have installed Apache 2.4.9 64-bit vc11 on Windows 2008R2 with mod_jk 1.2.39. I have mod_proxy and mod_proxy_http enabled. I have mod_jk to proxy Tomcat which serving the LSDS.

Apache, Tomcat, LSDS/LSCS is all currently running on the same server.

I'm on TS 7.3.2.

I tried to proxy / to a subfolder in Tomcat, but I also need to exclude other folders from the proxy. I've tried all variations using the exclude(!) descriptor, but nothing seems to work. Below is my virtual host configuration.

Has anyone ever notice the proxy exclusion descriptor to not work?

< VirtualHost *:80 >
ServerAdmin myemail
DocumentRoot "D:/Apache24/htdocs"
ServerName sitename.org
ServerAlias *.sitename.org
ErrorLog "logs/sitename.error.log"
CustomLog "logs/sitename.access.log" common
ProxyRequests off

< Proxy * >
Order deny,allow
Allow from all
< /Proxy >

ProxyPass /folder1/ http://127.0.0.1/html/siteroot/folder1/
ProxyPass /site-resources !
ProxyPass /site-assets !
ProxyPass / http://127.0.0.1/siteroot/

JkMount /* lsds_worker
< /VirtualHost >

My access log show the following message with the above configuration...

srcIP - - [14/May/2014:08:30:05 -0700] "GET / HTTP/1.1" 502 379
127.0.0.1 - - [14/May/2014:08:30:05 -0700] "GET /siteroot/ HTTP/1.1" 502 391
127.0.0.1 - - [14/May/2014:08:30:05 -0700] "GET /siteroot/siteroot/ HTTP/1.1" 502 403
127.0.0.1 - - [14/May/2014:08:30:05 -0700] "GET /siteroot/siteroot/siteroot/ HTTP/1.1" 502 415
127.0.0.1 - - [14/May/2014:08:30:05 -0700] "GET /siteroot/siteroot/siteroot/siteroot/ HTTP/1.1" 502 427
127.0.0.1 - - [14/May/2014:08:30:05 -0700] "GET /siteroot/siteroot/siteroot/siteroot/siteroot/ HTTP/1.1" 502 439
127.0.0.1 - - [14/May/2014:08:30:05 -0700] "GET /siteroot/siteroot/siteroot/siteroot/siteroot/siteroot/ HTTP/1.1" 502 451
127.0.0.1 - - [14/May/2014:08:30:05 -0700] "GET /siteroot/siteroot/siteroot/siteroot/siteroot/siteroot/siteroot/ HTTP/1.1" 502 463
127.0.0.1 - - [14/May/2014:08:30:05 -0700] "GET /siteroot/siteroot/siteroot/siteroot/siteroot/siteroot/siteroot/siteroot/ HTTP/1.1" 502 475
127.0.0.1 - - [14/May/2014:08:30:05 -0700] "GET /siteroot/siteroot/siteroot/siteroot/siteroot/siteroot/siteroot/siteroot/siteroot/ HTTP/1.1" 502 487
127.0.0.1 - - [14/May/2014:08:30:05 -0700] "GET /siteroot/siteroot/siteroot/siteroot/siteroot/siteroot/siteroot/siteroot/siteroot/siteroot/ HTTP/1.1" 502 499
127.0.0.1 - - [14/May/2014:08:30:05 -0700] "GET /siteroot/siteroot/siteroot/siteroot/siteroot/siteroot/siteroot/siteroot/siteroot/siteroot/siteroot/ HTTP/1.1" 502 511

...the above just keeps appending until the server runs out of threads and I reboot apache. I've followed all of the Apache instructions and other examples, but the results are not as expected.

Is there something wrong with what I have done or should I be taking another approach?

Rick Poulin

You forgot a little something important in your rule:
ProxyPass / http://127.0.0.1:1776/siteroot/

nipper

You forgot a little something important in your rule:
ProxyPass / http://127.0.0.1:1776/siteroot/

Doh!

Migrateduser

You forgot a little something important in your rule:
ProxyPass / http://127.0.0.1:1776/siteroot/

Thank you.

I considered that, but I was thinking that since I was already proxying Tomcat with mod_jk via Apache, I should be able to keep using the Apache http instead of proxying from the Apache http to Coyote. I guess I was wrong. So I guess going from Apache to Coyote would make the use of mod_jk unnecessary?

Rick Poulin

So I guess going from Apache to Coyote would make the use of mod_jk unnecessary?

Correct. mod_proxy and mod_jk are two different ways of accomplishing the same thing in this case. mod_proxy simply isn't tied to a particular platform, so it gives you a bit more flexibility but perhaps doesn't pass as much request+server information through to Tomcat (information you don't typically need anyway).

Migrateduser

Thanks for the insight and advice.

I've reconfigured my vhost with the following for now and everything is working as desired. I'll probably spend a little more time looking for an alternative way to completely phasing out mod_jk and a better way to redirect non-matching requests to a 404 page instead of the lsds site selection page.

< VirtualHost *:80 >
ServerAdmin myemail
DocumentRoot "D:/Apache24/htdocs"
ServerName sitename.org
ServerAlias *.sitename.org
ErrorLog "logs/sitename.error.log"
CustomLog "logs/sitename.access.log" common

< Proxy * >
Order deny,allow
Allow from all
< /Proxy >

RewriteEngine on
RewriteRule ^/html/sitename/(.*) /$1 [L,R]
RewriteRule ^/sitename/(.*) /$1 [L,R]
RewriteRule ^/$ /default.page [L,R]

ProxyPreserveHost On
ProxyPassMatch ^/(.*\.page)$ http://127.0.0.1:1776/sitename/$1
ProxyPassMatch ^/folder1/(.*\.html)$ http://127.0.0.1:1776/html/sitename/folder1/$1

JkMount /* lsds_worker
< /VirtualHost >