| Previous | Next |
| HTTP_STATUS_AMBIGUOUS | HTTP_STATUS_REDIRECT |
HTTP_STATUS_MOVED
Clients should update stored links when appropriate and follow the Location header. A 301 can be cached, so an accidental redirect may persist in browsers and intermediaries after a configuration change.
For non-idempotent methods, define the intended method behavior explicitly. If preserving the method and request body matters, 308 is the stricter permanent redirect status.
Operational meaning of HTTP 301 for HTTP_STATUS_MOVED
HTTP 301 (this result) is a redirection response. AllStat records its meaning as “301 Moved Permanently”. Interpret it with the request method, selected representation, response headers, and the specification or product that defines the code; the number alone does not prove that application work completed.
Client and server handling
- Apply the method-rewrite and caching rules defined for it, not a generic redirect rule.
- validate the Location target and prevent redirect loops across proxies or canonicalization layers.
- log the original URL, target URL, method, and cache decision.
For telemetry, record HTTP 301, method, authority, route template rather than secrets, response headers relevant to caching or retry, latency, upstream identity, and whether the response originated at the application or an intermediary.
Looking for a different code? Search another status or error code.