Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Posted on
- Daniel Greene
August 22, 2006, 2:44 pm
rate this thread
I haven't been on this newsgroup in years. Hello again to village
elders Lars Eighner, Alan Flavelle, and Jukka Korpela! :-)
What brings me back? I was using the W3C QA to validate my XHTML the
other day, and I came across this "tip of the day" called "Use standard
redirects: don't break the back button!" It said, "If you want
http://www.example.org/foo to actually display what's at
http://www.example.org/bar you should NOT [emphasis mine] use "refresh"
techniques like :
<META HTTP-EQUIV=REFRESH CONTENT="1; URL=http://www.example.org/bar ">."
Well, I'll be damned! I never knew that! It says to "Use HTTP redirects
instead." Shucks! I'm just a lowly XHTML/CSS author who don't know
nothin' 'bout birthin' babies-- I mean writing .htaccess files with
mod_rewrite! I tried following the links and reading about "redirect"
and mod_rewrite, really I did, but it just didn't make sense to me.
Now, I've always depended on the kindness of strangers, so I am posing
my dillema here in the hope that someone can tell me what to do in
I would like to establish the following redirects "the right way":
Can anyone tell me what code to write, or point me in the right
direction? I have already spent two hours reading what is Greek to me
and I still don't know exactly what to do. FYI, my host, "pair
Networks," uses Apache servers.
Lowly author of one of the first documents on the Web ever to use CSS:
Re: Using "standard redirects" so as not to "break the back button"
The newsgroup alt.apache.configuration would be a good place to start.
You could also Google for this:
htaccess redirect example
Don't forget that redirects must respond with a fully-qualified URL, not
a relative one.
Whole-site HTML validation, link checking and more