 | | Re: Stick in the mud...
|
| (...) I'm of two minds on this. :) It's not so bad when a server adds a trailing slash when someone types a URL in wrong by hand (like something they saw printed wrong on purpose in a print advertisement), but when a server allows _written_ URLs (...) (26 years ago, 13-Jun-00, to lugnet.admin.general)
| | |  | | Re: Stick in the mud...
|
| (...) If I were paying for a website to be designed for me for a commercial purpose, I'd want it designed to maximise the ease of use and to make any user feel comfortable - I doubt this would include lecturing users on web use. Scott A (...) (26 years ago, 13-Jun-00, to lugnet.admin.general)
| | |  | | Re: Stick in the mud...
|
| (...) I think trailing slashes should be optional by specification. Even if they are not optional in the spec, it is optional in the De Facto spec given the existing base of installed servers that handle it gracefully (to the end user). It would be (...) (26 years ago, 13-Jun-00, to lugnet.admin.general)
| | |  | | 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)
| |