Charles Lindsey wrote:
Well this is not the first time someone has proposed a structured header
with a URI in it, surely? So what has been done about this on previous
occasions? Parentheses in URIs are not all that common, so they could be
escaped. Or else the whole thing could be put inside a quoted-string.
RFC 2017 provides for URIs in parameters. RFC 2557 uses URIs in a structured
field. 2557 syntax is broken because it allows comments (this has been
discussed on the MHTML list). RFC 2369 uses URIs in various List- (structured)
fields. 2369 uses a quoting mechanism which permits comments outside of the
quoted URIs.
Using angle-brackets would doubtless also be a good idea, though I do not
think that on its own would allow comments to appear outside of the angle
brackets with parentheses inside being treated differently.
See RFC 2369. The quoting mechanism differentiates what is quoted (the
URI) from what is not quoted (commas in the case of lists, whitespace,
line folding, comments).
Long URIs are a pain in message/article bodies too. Is there any
possibility that those responsible to fixing the format of URIs could
include a folding mechansim? I do not like the idea of fixing what is a
more widespread URI problem within just a few particular email headers.
Whitespace and CRLF are not permitted in URIs. So folding isn't a problem.
See RFC 2396 Appendix E.
#################################################################
#################################################################
#################################################################
#####
#####
#####
#################################################################
#################################################################
#################################################################