 | | Re: Stick in the mud...
|
| (...) On servers where URLs map directly to filespecs, you can't have both /foo/bar and /foo/bar/ unless the underlying filesystem differentiates between the two. I'm not aware of any filesystems which simultaneously allow both /foo/bar and (...) (26 years ago, 13-Jun-00, to lugnet.admin.general)
| | |  | | Re: Stick in the mud...
|
| (...) In this example, if /foo/bar doesn't exist the user should get what /foo/bar/ points to, one way or another. Not a page to help them get to it. Either redirect (current practice) or rewrite (possible option) /foo/bar to /foo/bar/. If you (...) (26 years ago, 13-Jun-00, to lugnet.admin.general)
| | |  | | Re: Stick in the mud...
|
| (...) I agree that this is ideal in cases where the user may have mis-typed the URL by hand (or had been given the wrong URL from, say, a print ad in a magazine, and they typed it in by hand). I'm not sure it's ideal for cases where someone (...) (26 years ago, 13-Jun-00, to lugnet.admin.general)
| | |  | | Re: Stick in the mud...
|
| (...) 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. Given the way web pages currently work, I think it's important to keep from breaking web pages. To this extent, I have (...) (26 years ago, 13-Jun-00, to lugnet.admin.general)
| | |  | | Re: Stick in the mud...
|
| (...) Oh goody, the xoom factor... What is really needed is a protocol to inform the owner of the referring page that they have a bad link. (26 years ago, 13-Jun-00, to lugnet.admin.general)
| |