fiversen wrote:
Hello,
I have a site for the collegue with a football winning game.
..fussball.html
there I redirect the user to an cgi-page
../f11.cgi
>From time to time I change the cgi-pages,
so the redirection goes to
.../f12.cgi
If I understand correctly, fussball.html is a page that sometimes
redirects to f11.cgi, and sometimes f12.cgi, and your problem is that,
people should bookmark fussball.html, but actually bookmark either f11.cgi
or f12.cgi.
This is the difference between HTTP 301 and HTTP 302 redirections.
HTTP 301 for fussball.html would mean: Resource moved to f11.cgi (or
f12.cgi), forever. Don't use anymore fussball.html, bookmark f11.cgi (or
f12.cgi).
This is not what you want.
You want a HTTP 302.
HTTP 302 means: fussball.html is the right name for the resource, however,
for this current access, you should look at f11.cgi (or f12.cgi). If
you've to bookmark the page, please, bookmark fussball.html, not f11.cgi
(or f12.cgi).
So, an HTTP 302 redirection is exactly what you need.
The fact that buggy user agents tend to interpret HTTP 302 as if it were
HTTP 301 redirections is a real problem. If you want to support these
buggy user agents, you may on the server side, dump the contents of the
data produced by f11.cgi or f12.cgi when the fussball.html resource is
requested, without any redirection.
Please, read:
http://www.w3.org/Protocols/rfc2616/...0.html#sec10.3 http://www.w3.org/DesignIssues/UserAgent.html
--
If you've a question that doesn't belong to Usenet, contact me at
<ta*****************@yahoDELETETHATo.fr>