diff options
author | Eric Wong <normalperson@yhbt.net> | 2009-12-19 01:05:41 -0800 |
---|---|---|
committer | Eric Wong <normalperson@yhbt.net> | 2009-12-19 01:12:22 -0800 |
commit | 05fa45e54b0a6033250249ec0ed2009d4dbacf48 (patch) | |
tree | f33bba0dc9662991971bc539d39eaa75767c6195 /local.mk.sample | |
parent | 4c8c891b76c2a44a0ae76eea8f07934b984caab0 (diff) | |
download | unicorn-05fa45e54b0a6033250249ec0ed2009d4dbacf48.tar.gz |
This is not explicitly specified or listed as an example in in rfc2616. However, rfc2616 section 3.2.1 defers to rfc2396[1] for the definition of absolute URIs, so the userinfo component should be allowable, even if it does not make any sense. In the real world, previous versions of Mongrel used URI.parse() and thus allowed userinfo, so we also have precedence to allow userinfo to be compatible *in case* our interpretation of the RFCs is incorrect. This change is unfortunately needed because *occasionally* real clients rely on them. Reported-by: Scott Chacon [1] rfc3986 obsoletes rfc2396, but also includes userinfo
Diffstat (limited to 'local.mk.sample')
0 files changed, 0 insertions, 0 deletions