in reply to Re: print and redirect
in thread print and redirect

This works fine,

However is it better coding practise for me to write the following? 

<html>
<head>
<meta http-equiv="refresh" content="0;url=http://redirect.url.here?any
cgi=options&here=too">
</head>
<body></body>
</html>

[download]

rather than just the meta refresh line

Replies are listed 'Best First'.
Re: Re: Re: print and redirect
by Boldra (Curate) on Apr 10, 2001 at 20:03 UTC
    In general I would say no, avoid http-equiv headers if you can modify the real http headers.

    However, it depends why you are redirecting, using http-equiv headers gives you the ability to include javascript etc. Using the 'real' http headers gives proxies a better chance of understanding what you're doing, and theoretically they could read the http header and prepare the redirect before the browser asked for it. I have no idea if this actually happens.

    I beleive that the w3 position is to avoid http-equiv headers.

    (Did I understand your question correctly??)
[reply]
      Yes you understood fine, I will now try to include the redirect and cookie in the HTTP header itself
[reply]

In Section Seekers of Perl Wisdom