426 UPGRADE REQUIRED

The server won’t play out the request utilizing the present convention however may be happy to do as such after the customer moves up to an alternate convention. 

The server MUST send an Upgrade header field in a 426 reaction to show the required protocol(s)

Model: 

HTTP/1.1 426 Upgrade Required

Upgrade: HTTP/3.0

Connection: Upgrade

Content-Length: 53

Content-Type: text/plain

This service requires use of the HTTP/3.0 protocol.

This administration requires utilization of the HTTP/3.0 convention.

429 TOO MANY REQUESTS

The client has sent an excessive number of requests in a given measure of time (“rate restricting”). 

The reaction representations SHOULD incorporate subtleties clarifying the condition, and MAY incorporate a Retry-After header showing to what extent to hold up before making another request. 

For instance: 

HTTP/1.1 429 Too Many Requests

Content-Type: text/html

Retry-After: 3600

<html>

  <head>

    <title>Too Many Requests</title>

  </head>

  <body>

    <h1>Too Many Requests</h1>

    <p>I only allow 50 requests per hour to this Web site per

    logged in user. Try again soon.</p>

  </body>

</html>

Leave a Reply