Y wrote:
André,
thank you for pointing me in the right direction. The problem was that
my ip address is pointing to a different name on the local dns server of
my provider. The behaviour is correct when I use that name instead.
Would URL rewritting be the way to go to temporarly correct this (before
the domain transfer to my provider is completed)?
I am not quite sure that I really understand your explanation above.
But for the fundamentals, you have to keep the following in mind.
Many problems that look like browser problems or server problems can be
due in fact to "name resolution" (DNS) issues, and you must look at them
really in a step-by-step fashion :
When you tell your browser to fetch an object, for example
"http://myhost.company.com/subdir/object.html";, what your browser really
does is :
1) separate the URL above into components :
- the "protocol" (http://)
- the hostname (myhost.company.com)
- the URI (/subdir/object.html)
2) resolve the hostname into an IP address
(translate, with help of your local "hosts" file first, and if not
found there, via the DNS system, that hostname into a numerical IP
address). Say the end result of this is 100.100.100.100.
3) open a TCP/IP connection with that IP address
(note : *with that IP address*, not with the hostname)
4) send over that connection a request that looks like this :
GET /subdir/object.html HTTP/1.1
Host: myhost.company.com
.. (other things) ..
5) wait for an answer
Notice that the "GET" request sent is *not*
http://myhost.company.com/subdir/object.html
it is just
/subdir/object.html
Now, the server that is at the IP address 100.100.100.100 receives this
request, reads the URI requested in the first line, and reads the second
line with
Host: myhost.company.com
It will use this second line to find the appropriate virtual server, and
then my previous explanation applies.
But what the above means is that, if your browser somehow translates the
hostname "myhost.company.com" into an IP address, then
*that will be the IP address to which the request will be sent*
(whether that server knows anything about "myhost.company.com" or not)
and it means that if this is not the server that you expect, there is
nothing that that server can do about it.
Now, to address your particular problem directly, possibly (if I
understood this right) :
If the problem is that at this point, your browser is receiving, from
the DNS system, the wrong IP address for the host "myhost.company.com",
and if you can modify your local "hosts" file, then it is possible to
temporarily "fool" your browser into translating that hostname
differently. That is because on your workstation, the local part of the
DNS system will look first in the local hosts file, before asking other
DNS servers to translate the name.
So :
- add the following line to your local hosts file :
99.99.99.99 myhost.company.com
(adapt the IP address and name to what you want; if the host is really
your local workstation e.g., put 127.0.0.1 there)
- then restart your browser
The "hosts" file under Windows is at
c:/windows/system32/drivers/etc/hosts, and under Unix/Linux at /etc/hosts.
Please understand that this is purely a temporary hack, it will affect
only your workstation, as as soon as the DNS system works correctly, you
should remove this line again.
André
---------------------------------------------------------------------
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]
