April 9, 2006 at 9:15AM This server treats “Content-Location” oddly.
I’m not sure if this is an IIS 6 problem or a ColdFusion 5 problem, but one of the two of them is deciding to mangle my response headers if I add a Content-Location header to my response, interpreting it as a Location header and changing my response from a 200 OK to a 302 Found, causing it to redirect temporarily.
This is not how it’s meant to work! Content-Location is for specifying resources which are variant representations of the entity represented by the request URL, i.e. “that over there contains the same information as this here, but in a different form”. It doesn’t mean “bog off over there for now”.
I wanted to use it with my feeds, but that appears to be out of the question. Am I reading the RFC incorrectly, or is the server just acting the maggot?
No comments.