Subject:
|
Re: Stick in the mud...
|
Newsgroups:
|
lugnet.admin.general
|
Date:
|
Wed, 14 Jun 2000 00:03:58 GMT
|
Viewed:
|
1467 times
|
| |
|
|
In lugnet.admin.general, Todd Lehman writes:
> > Except that it's a pain to get a web page author to fix broken links on
> > their page which is effectively what you're saying.
>
> Oh, I didn't mean to suggest that /foo/bar should give a 404 error (page not
> found) if the HTTP referrer was from another webpage, I just meant that I
> don't believe it's an ideal solution to give a 301 (automatic redirect) in
> that case.
I hoped you didn't plan to give a 404 or a blank page, what I was saying is
that it would be annoying to be using someone else's page of links (because
it's so complete) and always get a "lecture" page until you can convince them
to fix it. Of course, in some ways, the pain of using a page with broken links
is why I ended up making my own pages of links, I got tired of all the broken
links on the Everything LEGO links page.
>
> > Given the way web
> > pages currently work, I think it's important to keep from breaking web
> > pages.
> >
> > To this extent, I have put redirector code into .../index.html in my web
> > pages since I mostly don't have actual content in the index.html page.
>
> Ahh, cool! So if someone links to
>
> http://www.foo.bar/glorp/gonk/zoop/index.html
>
> your page redirects them to the canonical URL?
>
> http://www.foo.bar/glorp/gonk/zoop/
>
> That's pretty cool.
Actually, it's that my LEGO page is:
http://www.mindspring.com/~ffilz/Lego/Lego.html
And I have http://www.mindspring.com/~ffilz/Lego/index.html do a redirect to
the correct page.
One thing which can also be annoying with some auto-redirects is that it keeps
you from using the back button to back up to before the page since by the time
you click it, the redirect has put you to the next page. I think this is due
to a zero delay on the redirect method I use in my index.html pages.
Of course if one really wants to get out of hand with the user friendliness,
you should also do a case insensitive match if a page doesn't seem to be
found. I really hate case sensitivity on file names. I can perhaps understand
it for identifiers in a program, but how is a non-technical user supposed to
know what the difference between foo.txt and Foo.Txt is? I'm not sure I like
case sensitivity in passwords either, but at least there, you're chosing your
own password, and I can see some advantage to doubling the alpha character set
(though I wonder how much it helps if one is encouraged to not use words and
names even when doing simple digit subsitutions and non-first letter
capitalizations - but we really don't need to revive that dead horse...).
Frank
|
|
Message has 1 Reply:
 | | Re: Stick in the mud...
|
| (...) Nope, definitely not! (...) Aha, I see. OK. BTW, any particular reason why to use the form (2 URLs) One thing which can also be annoying with some auto-redirects is that it (...) It depends on which type of redirect you use. If you use a real (...) (24 years ago, 14-Jun-00, to lugnet.admin.general)
|
Message is in Reply To:
| | Re: Stick in the mud...
|
| (...) Oh, I didn't mean to suggest that /foo/bar should give a 404 error (page not found) if the HTTP referrer was from another webpage, I just meant that I don't believe it's an ideal solution to give a 301 (automatic redirect) in that case. (...) (...) (24 years ago, 13-Jun-00, to lugnet.admin.general)
|
85 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
