Subject:
|
Re: Stick in the mud...
|
Newsgroups:
|
lugnet.admin.general
|
Date:
|
Wed, 14 Jun 2000 01:15:07 GMT
|
Viewed:
|
1531 times
|
| |
|
|
In lugnet.admin.general, Todd Lehman writes:
> BTW, any particular reason why to use the form
>
> http://www.foo.bar/zort/blurfl/blurfl.html
>
> over
>
> http://www.foo.bar/zort/blurfl/
>
> ?
I guess I just don't like having the document be in a file "index.html", but
want a directory with related documents.
> > 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.
>
> It depends on which type of redirect you use. If you use a real redirect
> using 301 in an HTTP 'Location:' header, it doesn't have that unwanted
> side-effect.
Is that something one can access by creating an html file, or do you have to
have access to the web server code in some way (or some special support in the
web server)?
> > 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?
>
> Any user can plainly see that 'f' and 'F' are different characters?
But how are they supposed to know that Foo.Txt is the version formatted for
some obscure program while foo.txt is the plain text file? I guess my question
is more, why would you ever need to have two files whose names are only
distinguished by case (ok, I can think of one reason, having a document and a
directory for sub-sections of that document having the same name in an
environment where file extensions aren't being used, thus "foo" would be the
main document, "FOO" would be the directory which contains the sub-documents
and images included by "foo").
> BTW, case-insensitive filename matching in URLs has the same evil problem as
> the missing / with regard to link colorings.
But if the standard were case insensitive file names, presumably the link
coloring code would use a case insensitive match to see if the link is the
same.
Other things which could cause problems with link matching:
- redirects which re-direct specific host names to some portion of a file
hierarchy under the primary host name
- situations where the browser automatically fixes apparently defficient host
names (do any browsers allow you to shortcut links by having the a link like
"lugnet", which if typed into at least IE and Navigator will send you to
"http://www.lugnet.com/"? Looks like the answer is no since such a thing is a
local reference and it doesn't work for "http://lugnet" in either case)
Frank
|
|
Message has 1 Reply:
 | | Re: Stick in the mud...
|
| (...) I don't know of any browsers that allow it but there are tools that let you do it. For Example: (URL) is an addon to your browser that lets you use aliases for finding pages. In Networds case you have to register a "netword" and its link and a (...) (24 years ago, 14-Jun-00, to lugnet.admin.general)
|
Message is in Reply To:
| | 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)
|
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
|
|
|
|
