Re: [users@httpd] Why doesn't Apache bind socket to vhost's IP addr.?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Nick Kew wrote:
On Wednesday 01 March 2006 13:39, Ralph.Grothe@xxxxxxxxxxxxxx wrote:
Is there a way to restrict the forked servers for this vhost
while keeping the higher numbers for the public webserver?
That doesn't make sense.  None of your children are "for" either
this vhost or the public webserver; they just serve whatever requests
they receive.

As nick pointed out this does not make sense as the vhost is only
known after the connection is established.

GET / HTTP/1.1
Host: www.foo.tld
...

If you really want this, then run two server process pools on two IP's.
Note that a virtual reverse proxy may help but because apache has a connection queue, you may end up with more front end connections than
the "limited" backend can handle - if you get the timeouts wrong.

There are other options and I am sure someone will chime in :-)

Jacqui

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx



[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux