Yes it works in Apache - try it!
You could also read the Apache documentation on Content
Negotiation. The following is a quote
---------------------------------------------------------
Note on hyperlinks and naming conventions
If you are using language negotiation you can choose between
different naming conventions, because files can have more than
one extension...

<snip>

Looking at the table above you will notice that it is always
possible to use the name without any extensions in an hyperlink
(e.g., foo). The advantage is that you can hide the actual type
of a document rsp. file and can change it later, e.g., from html
to shtml or cgi without changing any hyperlink references.
---------------------------------------------------------

On how it resolves conflicts?
Not documented, but a quick fiddle seems to indicate
that it does the following:

  if (no_specific_type_requested()) {
    get list of possible files in ALPHABETICAL order
    if (file_is_recognised_mime_type())
      return this file

recognised mime types come from /etc/mime.types

Regards
Jeff

-----Original Message-----
From: Harshdeep S Jawanda [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 22, 2001 11:06 AM
To: Jeff Armstrong
Cc: [EMAIL PROTECTED]
Subject: Re: [PHP] files with html extension



Jeff Armstrong wrote:

>  This is exactly why http://www.w3.org recommend that you DONT
>  SPECIFY A FILE TYPE TYPE in your HREFs.

But doth that actually work - how many web servers are able to handle this
type
of link correctly?

Ummm... and what happens (or is supposed to happen) to resolve xxx.html and
xxx.php?

--
Regards,
Harshdeep Singh Jawanda.



--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]


-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to