[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On Sat, Nov 28, 2009 at 9:06 PM, Adrian Midgley wrote:
> http://osborne.defoam.net gets a page served from the numeric IP address
> http://77.100.103.108/
> http://osborne.defoam.net/blog gets a 404
> http://77.100.103.108/blog ; gets waht I want, which is (a php page
> redirecting to where the blog is now)
>
> What do I have to do to serve http://77.100.103.108/blog in response to a
> request for http://osborne.defoam.net/blog ?
osborne.defoam.net resolves, via its DNS A record, to the IP address
77.92.80.174.
So http://osborne.defoam.net/ sends a HTTP request to 77.92.80.174.
The domain osborne.defoam.net is part of this request and, for some
reason, the web server responds to such a request with a 301 "moved
permanently" response and the redirection URL http://77.100.103.108/
The URL http://osborne.defoam.net/blog sends a HTTP request to the
same IP address, but the different path ("/blog" instead of "/")
results in the server giving a 404 error.
This might help you understand why things don't work as you'd expect
them to work, but what is really the matter can not be answered
without looking at the configuration of the web server(s) involved.
But it does appear that changing the DNS A record for
osborne.defoam.net to 77.100.103.108 could solve the problem.
Hope that helps a bit.
Martijn.
--
The Mailing List for the Devon & Cornwall LUG
http://mailman.dclug.org.uk/listinfo/list
FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html