On 07/25/2013 11:05 AM, Dennis Jarecke wrote:
> I think what is going on here is that somehow pound is stripping off the
> domain pound_example.info such that the proper virtual host is not being
> invoked
Hi,
I just tried this on a VM and pound does in fact sends the host-header.
This is my pound.cfg:
# ---------------------------
ListenHTTP
Address 192.168.40.4
Port 8888
Service
BackEnd
Address 192.168.40.4
Port 80
End
End
End
# -----------------------------
And now the httpd.conf part:
# --------------------------------
NameVirtualHost *:80
<VirtualHost *:80>
ServerAdmin [email protected]
DocumentRoot /var/www/html/site1
ServerName site1
ErrorLog logs/site1-host.example.com-error_log
CustomLog logs/site1-host.example.com-access_log common
</VirtualHost>
<VirtualHost *:80>
ServerAdmin [email protected]
DocumentRoot /var/www/html/site2
ServerName site2
ErrorLog logs/site2-host.example.com-error_log
CustomLog logs/site2-host.example.com-access_log common
</VirtualHost>
#--------------------------------------------
I added site1 & site2 to my /etc/hosts (pointing to the VM where Apache
& Pound is running) and I could hit both sites on my browser with
http://site1:8888 & http://site2:8888 (showing their respective content).
In a nutshell, check your Apache VirtualHost configuration since pound
does indeed sends the host-header as you can see.
On the other hand, and I don't think this is related to your issue, you
might want to check how you define your VirtualHosts. If you define an
ip to be used for Name-based VirtualHosting like this:
NameVirtualHost 1.2.3.4:80
... then you'll have to match that ip in the VirtualHost definitions
like this:
<VirtualHost 1.2.3.4:80>
AFAIK, you can't mix them (wildcards and IPs).
--
Jorge
--
To unsubscribe send an email with subject unsubscribe to [email protected].
Please contact [email protected] for questions.
