httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 44779] New: Using commas and semicolons for content negotiation instead of file extensions
Date Tue, 08 Apr 2008 14:00:33 GMT

           Summary: Using commas and semicolons for content negotiation
                    instead of file extensions
           Product: Apache httpd-2
           Version: 2.3-HEAD
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mod_negotiation


urn:ietf:rfc:3986 says to use commas and semicolons instead of dots when
dealing with things such as content negotiation. (Actually, it does not say
that at all; but it is the point of that RFC.)

Look at this example where all bits of information used in the negotiation
process for ../resource is separated with dots.


Then look at this example where all the keys but the actuall file
extension---though note that the example has two extensions---are separated
with commas instead.


Another approch form urn:ietf:rfc:398 is to use semicolon and value--key pairs.
Again, note that the file has two extensions realted to format.


Both methods allow for negotiation matching a file path AND for negotiation
that does not match the file path exactly. For example would both the below
example still match the correct file because the information is properly
separated from the both the file name and file extension.


...I really hope this will be implemented soon. Ths would clean up all the
messy URIs of the world in an instance. (Well, at least it would prevent new
URIs from being dirty.)

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message