W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2010

Re: Same resource exposed over HTTP and HTTPS

From: Nathan <nathan@webr3.org>
Date: Thu, 20 May 2010 01:37:17 +0100
Message-ID: <4BF4843D.70403@webr3.org>
To: Henrik Nordström <henrik@henriknordstrom.net>
CC: HTTP Working Group <ietf-http-wg@w3.org>
Henrik Nordström wrote:
> ons 2010-05-19 klockan 15:36 +0100 skrev Nathan:
> 
>> I've hit on a scenario where we'd like to identify resource with http 
>> scheme URIs; where safe methods are exposed via standard HTTP, whereas 
>> unsafe methods (in this case PUT and DELETE) would be exposed via HTTPS.
> 
> Content-Location can be used to hint about this. If both http and https
> respond with the same https content location then clients will have a
> hint that they are the same and also a hint that this location should be
> used when updating the resource.

I appear to have hit a 'feature' that I've never seen before, and isn't 
documented anywhere in HTTPbis (from what I can see).

Short version in apache 2.2.8 is now sending me back the following:

   Content-Location: webr3.rdf, https://open.gs/users/webr3.rdf

Haven't done anything particularly special to produce this, all I've 
done is enable mod_cern_meta and add the following to a meta file:

   Content-Location: https://open.gs/users/webr3.rdf

The obvious question then, apache / mod_cern_meta bug - or something 
HTTP related.

Best,

Nathan
Received on Thursday, 20 May 2010 00:38:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:18 GMT