It's that hotfix you must have.
Then, if it works and listen 80 doesn't behave, I suspect that MS is still
treating each loopback IP as disassociated from 'all' 0.0.0.0.
So try this instead
listen 127.0.0.1:80
listen 127.0.0.2:80
...
listen 127.0.0.5:80
Oh, and take a look at using windows\system32\drivers\etc\hosts on the
machine she uses to set up
127.0.0.1 www.myshop.local www.thatshop.local
and then use named hosts to map www.myshop.local etc each to their own vhost.
It's alot easier than by-ip, and you can even use a real (local) ip of the
box apache is running on (listening to that port) and copy around these lines
to the other boxes, so she can compare ie to firefox etc etc.
Mark Kalmus wrote:
We have a handful of ecommerce sites for my wifes cottage industry
business. We are developing the sites on a PC running Apache v.1.x, but
after having to install XP SP2 so her new Microsoft accounting software
would run, her VirtualHost addresses ceased to work, making site changes
arduous.
Previously, she had 127.0.0.1 through 127.0.0.5 as virtual websites that
she would develop and upload after testing to a live server. But now
only 127.0.0.1 is functioning (as localhost) and her PHP server-side
include statements are no longer working.
I’ve googled this issue to my heart’s content and remain stymied.
Microsoft has a KB hotfix that was to address the loopback failure
issue, but we still can’t get to her virtualhosts.
Any guidance you might offer would be greatly appreciated.
M Kalmus
---------------------------------------------------------------------
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: [EMAIL PROTECTED]
" from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
