 | | 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)
| |