301 MOVED PERMANENTLY

The objective asset has been allocated another lasting URI and any future references to this asset should utilize one of the encased URIs. 

Customers with interface altering capacities should naturally re-connect references to the successful request URI to at least one of the new references sent by the server, where conceivable. 

The server SHOULD produce a Location header field in the reaction containing a favored URI reference for the new lasting URI. The client operator MAY utilize the Location field an incentive for programmed redirection. The server’s reaction payload generally contains a short hypertext note with a hyperlink to the new URI(s). 

Note: For authentic reasons, a client operator MAY change the request strategy from POST to GET for the resulting demand. On the off chance that this conduct is undesired, the 307 Temporary Redirect status code can be utilized. 

A 301 reaction is cacheable as a matter of course; i.e., except if generally showed by the technique definition or unequivocal store controls.

Leave a Reply