Message226926
Wow. This is interesting. I thought that absolute URL support was only for proxies, but the spec you quote says clearly it should be supported as a transition towards always specifying the full URL. I guess they want to get rid of the Host: header?
In any case I would worry (a bit) that this might cause security issues if implemented as naively as shown in your patch -- the other components of the URL should probably be validated against the configuration of the server. Also I am wondering whether specifying a different port or protocol (e.g. HTTPS) should be allowed or not, and what to do with extraneous parts of the path (in particular the "#fragment" identifier). You should probably also be careful with path-less domain names -- IIRC some URL parsers produce "" as the path for e.g. "http://python.org".
Finally, AFAIK the HTTP 1.1 standard is full of ideas that few server implementations support, for various reasons, and it's possible that a future standard actually rescinds (or discourages) some features. Have you asked for the status of this particular feature? |
|
Date |
User |
Action |
Args |
2014-09-15 17:08:15 | gvanrossum | set | recipients:
+ gvanrossum, pje, mouad |
2014-09-15 17:08:15 | gvanrossum | set | messageid: <1410800895.52.0.547440899287.issue21472@psf.upfronthosting.co.za> |
2014-09-15 17:08:15 | gvanrossum | link | issue21472 messages |
2014-09-15 17:08:15 | gvanrossum | create | |
|