1:06 p.m.
I can't figure out where it comes into play, but VM's notion of the extent
of a URL is too greedy. In the emails they send out, discussion forums
often embed URLs in some [url]...[/url] tags, e.g.:
[url]http://www.google.com/[/url]
VM highlights the trailing "[/url]" as part of the URL, so it sends too much
to your browser if you click the highlighted text. I'm using VM 7.17 in
XEmacs 21.5.28. I've never seen a situation where "[" appears unencoded in
a URL, so even if it's valid to leave it unencoded I think you'd have fewer
problems if you kept it out of the match set when looking for the end of the
URL.
--
Skip Montanaro - skip(a)pobox.com - http://www.webfast.com/~skip/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
11:23 p.m.
skip(a)pobox.com wrote:
I can't figure out where it comes into play, but VM's notion of the extent
of a URL is too greedy. In the emails they send out, discussion forums
often embed URLs in some [url]...[/url] tags, e.g.:
[url]http://www.google.com/[/url]
VM highlights the trailing "[/url]" as part of the URL, so it sends too much
to your browser if you click the highlighted text. I'm using VM 7.17 in
XEmacs 21.5.28. I've never seen a situation where "[" appears unencoded
in
a URL, so even if it's valid to leave it unencoded I think you'd have fewer
problems if you kept it out of the match set when looking for the end of the
URL.
According to RFC 3986:
A host identified by an Internet Protocol literal address, version 6
[RFC3513] or later, is distinguished by enclosing the IP literal
within square brackets ("[" and "]"). This is the only place
where
square bracket characters are allowed in the URI syntax.
So, http://[192.168.0.1]/ is technically valid (and works in Firefox),
but I've never seen the square brackets actually used.
--
Glynn Clements <glynn(a)gclements.plus.com>
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
11:52 p.m.
Glynn> According to RFC 3986:
Glynn> A host identified by an Internet Protocol literal address,
Glynn> version 6 [RFC3513] or later, is distinguished by enclosing
Glynn> the IP literal within square brackets ("[" and "]").
This is
Glynn> the only place where square bracket characters are allowed in
Glynn> the URI syntax.
Glynn> So, http://[192.168.0.1]/ is technically valid (and works in
Glynn> Firefox), but I've never seen the square brackets actually used.
Thanks for pointing out that situation. In that case, the [...] should only
be allowed in the host portion of the URL, not in/after the path section.
Skip
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
2:30 a.m.
VM's URL matching is pretty basic; one big, hairy regexp as I
recall. See vm-url-regexp. Attack that if you want immediate
relief, but a real fix is going to require more sophistication in
the code I expect.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
3:26 p.m.
On Monday 24 September 2007, Glynn Clements wrote:
According to RFC 3986:
A host identified by an Internet Protocol literal address, version 6
[RFC3513] or later, is distinguished by enclosing the IP literal
within square brackets ("[" and "]"). This is the only place
where
square bracket characters are allowed in the URI syntax.
So, http://[192.168.0.1]/ is technically valid
Um, how so? 192.168.0.1 is an IPv4 address - the above quoted part says
enclosing in square brackets is allowed for IPv6 and later addresses only.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
12:23 a.m.
skip(a)pobox.com writes:
VM highlights the trailing "[/url]" as part of the URL, so
it sends too much
to your browser if you click the highlighted text. I'm using VM 7.17 in
XEmacs 21.5.28. I've never seen a situation where "[" appears unencoded
in
a URL, so even if it's valid to leave it unencoded I think you'd have fewer
problems if you kept it out of the match set when looking for the end of the
URL.
VM is externally maintained by Robert Fenk now, IIRC (I know Kyle
retired). If you don't see a response from the VM maintainers
shortly, feel free to bug us again, but for now XEmacs will leave it
up to VM (or other volunteers :^).
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
6:04 p.m.
skip(a)pobox.com wrote:
I can't figure out where it comes into play, but VM's notion
of the extent
of a URL is too greedy. In the emails they send out, discussion forums
often embed URLs in some [url]...[/url] tags, e.g.:
[url]http://www.google.com/[/url]
VM highlights the trailing "[/url]" as part of the URL, so it sends too much
to your browser if you click the highlighted text. I'm using VM 7.17 in
XEmacs 21.5.28. I've never seen a situation where "[" appears unencoded
in
a URL, so even if it's valid to leave it unencoded I think you'd have fewer
problems if you kept it out of the match set when looking for the end of the
URL.
FWIW, thunderbird is also greedy so this must be standard, probably an
RFP. I didn't look it up, but I know that <> can be used correctly like
<http://www.google.com/>
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
6059
days inactive
6060
days old
6 comments
6 participants
participants (6)
-
Glynn Clements -
Kyle Jones -
Rodney Sparapani -
Skip Montanaro -
Stephen J. Turnbull -
Ville Skyttä