What does HTTP status 430 (Header Fields Too Large 2) mean?

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.

Shopify API response codes

Operational meaning of HTTP 430 for HTTP_STATUS_HEADER_FIELDS_TOO_LARGE_2

HTTP 430 (HTTP_STATUS_HEADER_FIELDS_TOO_LARGE_2) is a client-error response. AllStat records its meaning as “430 Request Header Fields Too Large”. For HTTP_STATUS_HEADER_FIELDS_TOO_LARGE_2, 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 for HTTP_STATUS_HEADER_FIELDS_TOO_LARGE_2

• Treat HTTP_STATUS_HEADER_FIELDS_TOO_LARGE_2 as a condition visible at the request boundary; inspect authentication, syntax, preconditions, routing, and resource state before retrying.
• For HTTP_STATUS_HEADER_FIELDS_TOO_LARGE_2, preserve the response body and challenge or retry-related headers because they often carry the actionable reason.
• For HTTP_STATUS_HEADER_FIELDS_TOO_LARGE_2, automatic retry is safe only when the method and status contract allow it and the request has been corrected.

For telemetry, record HTTP 430, 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.