> Instead of doing an http redirect, I want to serve the page with a > modified url. I want to avoid the redirect for performance reasons. What do you want the client to do with future requests? Should a GET for uri_1 alway use uri_1, or should future requests use uri_2? Should POSTs to uri_1 alway use uri_1, or should future requests use uri_2?
The response code of 302 Moved Permanently might help if that is your intent: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.2 "The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs. Clients with link editing capabilities ought to automatically re-link references to the Request-URI to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise. The new permanent URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s). If the 301 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued. Note: When automatically redirecting a POST request after receiving a 301 status code, some existing HTTP/1.0 user agents will erroneously change it into a GET request. " ----- Original Message ----- From: "Martin Alley" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, June 18, 2004 10:48 AM Subject: http response header to alter requested page url? Hi, Is there an http response header to alter requested page url? Instead of doing an http redirect, I want to serve the page with a modified url. I want to avoid the redirect for performance reasons. Content-Location appears inappropriate because as rfc2616 says: "The Content-Location value is not a replacement for the original requested URI; it is only a statement of the location of the resource corresponding to this particular entity at the time of the request. Future requests MAY specify the Content-Location URI as the request- URI if the desire is to identify the source of that particular entity." NB In the scenario I am dealing with, the modified url will only differ in it's url params. If I was using http post instead of http get, I could freely modify the associated form data without a second thought, but I've gone down the get path (no pun intended). Sorry if this is an inappropriate question for this list. Martin
