| Previous | Next |
| HTTP_STATUS_RETRY_WITH | HTTP_STATUS_IIS_REDIRECT |
HTTP_STATUS_BLOCKED
Because 450 is vendor-specific, it should be interpreted together with the response body and the filtering product that produced it. It is not interoperable with the standard 4xx definitions.
For a user, the relevant action is to review the device or family-safety policy. For a site operator, capture the filtering product and request details rather than changing server routing or content blindly.
Because 450 is unregistered, software should not attach portable HTTP semantics to the number alone. If it appears in a trace, identify the component that generated it and preserve the response body or product-specific error details. Another proxy, server, or application can legitimately use the same unregistered number for a different purpose.
Looking for a different code? Search another status or error code.