| Previous | Next |
| HTTP_STATUS_TOO_MANY_REQUESTS | HTTP_STATUS_HEADER_FIELDS_TOO_LARGE |
HTTP_STATUS_HEADER_FIELDS_TOO_LARGE_2
The IANA registry does not assign HTTP status 430. In this case the AllStat source identifies Shopify, where a 430 response is used for a security rejection rather than as the standard 431 header-size status.
Read the response body and platform request ID, then inspect the request for traffic patterns or headers that a security layer can classify as malicious. Do not treat 430 as interoperable with 431.
Since 430 has no IANA-defined meaning, portable clients should treat the response as implementation-specific. If a product uses it for large headers, inspect that product's limits and the received header section. Do not automatically equate it with standardized 431 unless the generating component explicitly documents that behavior.
Looking for a different code? Search another status or error code.