 | | Re: Stick in the mud...
|
|
(...) OK, let's add "unaware" to that list; some users may be unaware that a URL is actually /foo/bar/ and perceive it instead as /foo/bar -- especially if the URL was printed wrong somewhere, such as a print ad. Note: If the server actually (...) (26 years ago, 13-Jun-00, to lugnet.admin.general)
|
| |
 | | Re: Stick in the mud...
|
|
(...) It's not that, Mike, it's that /castle is actually a valid URL of a valid webpage (it just happens to be empty). When I view that, it shows me a button which says "Start This Page" and I could click that and type in content onto that page if I (...) (26 years ago, 13-Jun-00, to lugnet.admin.general)
|
| |
 | | Re: Stick in the mud...
|
|
(...) Do you mean that if a browser requested some page /foo/bar which didn't exist, but a page /foo/bar/ existed, that it would be nice if the server output the content of /foo/bar/ when it was requested to serve /foo/bar ? If so, wouldn't that (...) (26 years ago, 13-Jun-00, to lugnet.admin.general)
|
| |
 | | Re: Stick in the mud...
|
|
(...) What filesystem allows file bar and directory bar in the foo directory? The only way to utilize the above hypothetical URL's is to use mod-rewrite (or similar). You could easially disable slash-optional rewrite when a mod-rewrite rule is (...) (26 years ago, 13-Jun-00, to lugnet.admin.general)
|
| |
 | | Re: Stick in the mud...
|
|
(...) wouldn't (...) /foo/bar/ (...) Optionally yes. The admin could choose the least expensive mode to operate in, redirect or rewrite (probably redirect now that you mention it). KL (26 years ago, 13-Jun-00, to lugnet.admin.general)
|
| |
 | | Re: Stick in the mud...
|
|
(...) Yeah, I've been wondering this too. It's pretty longstanding practice in unix that "ls /usr" and "ls /usr/" are going to get me exactly the same thing. For that matter, "stat /usr" and "stat /usr/" both get me the same thing.... And I'm (...) (26 years ago, 13-Jun-00, to lugnet.admin.general)
|
| |
 | | Re: Stick in the mud...
|
|
(...) Ah, that makes sense. Really, in order for the proposed ("/foo/bar" exactly equals "/foo/bar/") scheme to work, there needs to be _no_ default index.html file. Or rather, directory index files need to be special in some way. (Just like you'd (...) (26 years ago, 13-Jun-00, to lugnet.admin.general)
|
| |
 | | Re: Member benefits... ?
|
|
(...) OK, good idea! For now I put category links on (URL) the password center thingie and to the new pages thingie (at the top) and in the body of the page also added a link to the announcement about pages. (There hasn't been an official (...) (26 years ago, 13-Jun-00, to lugnet.admin.general, lugnet.people)
|
| |
 | | Re: Stick in the mud...
|
|
(...) More specifically try to create a file and a directory with the same parent and same name. It doesn't work on any operating system I know of (ok I haven't tried it on a Mac). KL (26 years ago, 13-Jun-00, to lugnet.admin.general)
|
| |
 | | 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)
|
| |
 | | Re: Stick in the mud...
|
|
(...) I'd go so far as to say the majority of users are "unaware" of this sort of thing. And it will remain that way, probably forever. Have you seen lots of print ads floating around that contain trailing slashes? And sorry if I seemed overly (...) (26 years ago, 13-Jun-00, to lugnet.admin.general)
|
| |
 | | 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. (...) (...) (26 years ago, 13-Jun-00, to lugnet.admin.general)
|
| |
 | | Re: Stick in the mud...
|
|
(...) What does Xoom do? (...) That would be awesome!!! --Todd (26 years ago, 13-Jun-00, to lugnet.admin.general)
|
| |
 | | Re: Stick in the mud...
|
|
(...) I've seen more without than with, but some of both. But more often than either, I've seen root-level URLs, often without the slash and even without the www prefix. :) (...) Ahhh, it's spring/summer cold season. :) Drink lots of hot chicken (...) (26 years ago, 13-Jun-00, to lugnet.admin.general)
|
| |
 | | Re: Stick in the mud...
|
|
(...) Isn't it possible for the server to generate a /foo/bar page when its requested, and see that /foo/bar/ exists, then auto-redirect the user to /foo/bar/, therefore evading this problem? -Tim (26 years ago, 13-Jun-00, to lugnet.admin.general)
|
| |
 | | Re: Stick in the mud...
|
|
(...) /foo/bar/ (...) someone (...) What's the difference between someone typing in a url into a browser and typing a url into a text editor? Not much, except perhaps the person typing it into a text editor should consider proper netiquette. A good (...) (26 years ago, 13-Jun-00, to lugnet.admin.general)
|