I've got W2K8R2 with IIS 7.5 on my internal lan with internal ip.
I've got an Apache 2.2 with mod_proxy and mod_ssl in my DMZ with public ip.
My FQDN is pointed at the Apache, which I use to proxy pass into my IIS on defined pathes.
If someone goes to https://web1.company.com/web/test.aspx
they arrive at the Apache server. Apache then sends the traffic to my IIS -> http://web1.domain.local/web/test.aspx
So far so good.
My problem is that if I call a webservice on my IIS using the public fqdn (https://web1.company.com/web/test.aspx
), my browsers (IE, Chrome, locally on the server and on my workstation on our office lan (internal, but different vlan)) waits 5 seconds before sending the request and displaying the text I the request will get from the webservice.
If I however uses the internal name (http://web1.domain.local/web/test.aspx
) the request is fetched and displayed imediatly
I have no problems pinging the servers.
I've also been checking the Apache server with tcpdump and it takes about 5 seconds before I see anything going to the apache proxy. If I try from my computer at home via internet (no vpn etc) I see a hit in tcpdump at once, and my info is displayed quick and nice, no 5 seconds delay.
Just for the record, here is the APache mod_proxy settings:
ProxyPass /web/ http://web1.domain.local/web/
ProxyPassReverse /web/ http://web1.domain.local/web/
It looks like IIS is waiting 5 seconds for something, or apache is delaying the request somehow, which I don't see on tcpdump (i've monitored the interface with the IP for my FQDN). I've also disabled IPv6 on my teamed NICs (only one NIC is active, the other one is standby) on IIS-server.
Any clues to why it's this strange?