type=<typecode> redux

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Bill_Melvin/SUNY%SUNY@esc.edu: "type=<typecode>, last for today I think"
• Previous message: Bill.Melvin@esc.edu: "[RESEND] type=<typecode> (RFC1738)"

Hi all,

slightly OT here but does this

> Extensive testing of current client applications demonstrated that
> the majority of deployed systems do not use the ";" character to
> indicate trailing parameter information, and that the presence of a
> semicolon in a path segment does not affect the relative parsing of
> that segment.  Therefore, parameters have been removed as a separate
> component and may now appear in any path segment.  Their influence
> has been removed from the algorithm for resolving a relative URI
> reference.  The resolution examples in Appendix C have been modified
> to reflect this change.

from RFC2396 mean that "type=<typecode>" has gone away or that it
can appear in any path segment? And what is the LWP/URI reading of
2396 re ;parameters? Hrmmm ....

/Bill

• Next message: Bill_Melvin/SUNY%SUNY@esc.edu: "type=<typecode>, last for today I think"
• Previous message: Bill.Melvin@esc.edu: "[RESEND] type=<typecode> (RFC1738)"