W3C home > Mailing lists > Public > uri@w3.org > January 2010

non-HTTP URIs in HTTP requests

From: Erik Wilde <dret@berkeley.edu>
Date: Wed, 06 Jan 2010 10:30:46 -0800
Message-ID: <4B44D6D6.6030601@berkeley.edu>
To: "uri@w3.org" <uri@w3.org>

i have a technical question about HTTP and URIs. my use case is that i 
am considering to use HTTP for the resolution of non-HTTP URIs, so that 
for example (this is my use case) a geo:37.0625,-95.677068 URI could be 
"resolved" via HTTP. regardless of the actual process (what "resolution" 
returns in the response), i am currently just trying to find out whether 
it would be legal to send a HTTP request like this:

GET geo:37.0625,-95.677068 HTTP/1.1

it seems to me that RFC 2616 does not prohibit such a use, but i am sure 
that a lot of people will dislike it for various reasons. however, 
currently i am just interested to figure out whether it's legal, and i 
think it is (not the geo: per se, which is not yet a standard, but the 
fact that there is a non-HTTP URI in the request). if i am mistaken, 
feedback would be greatly appreciated.


erik wilde   tel:+1-510-6432253 - fax:+1-510-6425814
        dret@berkeley.edu  -  http://dret.net/netdret
        UC Berkeley - School of Information (ISchool)
Received on Wednesday, 6 January 2010 18:31:22 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:13 UTC