- From: Mike Dierken <dierken@gmail.com>
- Date: Thu, 7 Jun 2007 09:17:17 -0700
- To: "Nicholas Shanks" <contact@nickshanks.com>
- Cc: "Julian Reschke" <julian.reschke@gmx.de>, ietf-http-wg@w3.org
> Images, and anything that refers to images would need to support it. > You may have existing content that is named foo-hires.jpeg and foo- > lowres.jpeg and want to switch between them without doing the > negotiation on the images themselves (so that old references don't > need to be fixed) Ahh, well there's yer problem right there... The "... so that old references don't need to be fixed..." is the issue. It turns out that on the Web it's much better to have two references and work on 'fixing up' the sources that point to one or the other. One concrete example is a caching proxy that has been taught to only look at the URI - without updating the implementation of all those existing caching servers, the wrong bits will be returned to clients that ask for "foo.jpg" because the cache hasn't been taught to look for this new header. In this case perhaps using the Vary header in a response may help, but I believe there are other areas where having different representations for the same URI may create problems.
Received on Thursday, 7 June 2007 16:17:28 UTC