449 Retry With
IIS code telling the client to retry after supplying additional information the server needs.
Status
HTTP/1.1 449 Retry With
Details
- Category: 4xx
- Status: Unofficial (Microsoft IIS). Not registered with IANA. A server, framework, or CDN convention.
- Specification: none, not defined by any RFC
- Cacheable: Not cacheable
- Response body: Allowed
- Retry: Retry only after changing the request
449 was introduced by Microsoft so a server could ask a client to resend a request with more information, for example additional parameters required by an extension. The details of what is missing are carried in the response body.
It never spread beyond Microsoft software and is rare even there.
Common causes
- A Microsoft server extension needed extra request data before it could act.
How to fix it
As the client
- Read the body to see what is required, add it, and resend.
As the server
- Prefer 400 or 428 with a clear description of the missing input, so non-Microsoft clients can act on it.
Examples
POST /service.asmx HTTP/1.1 Host: legacy.example.com HTTP/1.1 449 Retry With