| Technical note: | 10025 |
| Created: | 09/18/95 by Trip |
| Updated: | 11/01/95 by Brian |
| Product: | Netscape Navigator |
If you have a URL with a fragment in it, like this:
http://servername/path/file.html#fragment
to point to a specific location on a page (designated by an
<A NAME="..."> tag), that "#fragment" is stripped off the URL before
the browser contacts the server to ask for the page in question. Once
the browser gets the page, it "scrolls down" to the proper location on
the page.
This has two consequences:
(1) The server has no way of knowing what #fragment, if any, the
browser wants to get to, so it's not possible to log this in any way
on the server side.
(2) Netscape Navigator has a bug whereby if it receives a "302
Redirect" message telling it to look elsewhere for the file it wants
to load, it will forget any "#fragment" it wanted to scroll down to
when it loads the file from the new location. So if you are trying to
load "http://aaa/file.html#foo", and the server "aaa" sends back a
redirect that points the browser to "http://bbb/file.html", Netscape
Navigator will display "http://bbb/file.html" from the top instead of
from the location "#foo".
Copyright © 1996 Netscape Communications Corporation