Closed (duplicate)
Project:
Link
Version:
5.x-2.5
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
8 Apr 2009 at 18:34 UTC
Updated:
1 Mar 2010 at 01:02 UTC
RFC2396 (http://www.ietf.org/rfc/rfc2396.txt C.2) does not restrict the characters after the # symbol in URIs. The regex used to validate in the module restricts it with the following: (#[a-z0-9_\-\.~+%=&,$'():;*@\[\]]*) (line 865). There are live examples of sites using forward slashes after the # symbol, e.g. http://www.cnn.com/video/#/video/politics/2008/12/09/intv.madeleine.albr.... This fails the current validation in the module. At the very least the forward slash should be added to the allowed characters. Attached is a patch that makes this change.
| Comment | File | Size | Author |
|---|---|---|---|
| link.fragment.20090408.patch | 569 bytes | whurley |
Comments
Comment #1
jaydub commentedRelated to #323879: Facebook profile - not valid URL
Comment #2
jcfiala commentedJust raising this issue in the list so I'm reminded of it later.
Comment #3
japanitrat commentedAnd this one: #615642: "/" and "?" should be valid after anchor
Comment #4
jcfiala commentedI'm marking this as a duplicate of #615642: "/" and "?" should be valid after anchor, and I'll be marking that one as fixed in a minute.