Anonymous user
Talk:URL parser: Difference between revisions
m
corrected section header identification tag (fence).
(→hostname for arbitrary schemes: new section) |
m (corrected section header identification tag (fence).) |
||
Line 1:
Great task! The example URLs provide good coverage, but the example <tt> ldap://[2001:db8::7]/c=GB?objectClass=one&objectClass=two </tt> is invalid per RFC2255. For solutions exercising library code that knows about more URL structures than HTTP, this is distracting. I suggest replacing it with the example in RFC3986: <tt> ldap://[2001:db8::7]/c=GB?objectClass?one </tt> which is just as parseable under HTTP rules, but won't blow up a parser that understands the ldap scheme.
| |||