tech-invite   World Map     

IETF     RFCs     Groups     SIP     ABNFs    |    3GPP     Specs     Gloss.     Arch.     IMS     UICC    |    Misc.    |    search     info

ABNF grammars

 

ABNF for HTTP/1.1 – Hypertext Transfer Protocol – RFC 7230 to 7235

1  of  3

 

Here

 

Top

 

 

 

 

 

Next

 

RFC 7230HTTP/1.1:  Message Syntax and Routing
RFC 7231HTTP/1.1:  Semantics and Content
RFC 7232HTTP/1.1:  Conditional Requests
RFC 7233HTTP/1.1:  Range Requests
RFC 7234HTTP/1.1:  Caching
RFC 7235HTTP/1.1:  Authentication
supersede  RFC 2616 and revise the ABNF syntax for HTTP/1.1



Message_Format     Header_Fields     URIs_and_Request_Target     Transfer_Codings
Date_Time     Range_Units     Challenge_Response_Authentication     Miscellaneous

RFC 7230 – Section 3

Up

HTTP-message   =
start-line   =
request-line   =
status-line   =
method   =
HTTP-version   =
HTTP-name  /  DIGIT   "."   DIGIT

HTTP-name   =
%x48.54.54.50
; "HTTP", case-sensitive

message-body   =
reason-phrase   =
*( HTAB  /  SP  /  VCHAR  /  obs-text )

status-code   =
3DIGIT
; 1xx   Informational
; 100   Continue   [ RFC 7231 – Section 6.2.1 ]
; 101   Switching Protocols   [ RFC 7231 – Section 6.2.2 ]

; 2xx   Successful
; 200   OK   [ RFC 7231 – Section 6.3.1 ]
; 201   Created   [ RFC 7231 – Section 6.3.2 ]
; 202   Accepted   [ RFC 7231 – Section 6.3.3 ]
; 203   Non-Authoritative Information   [ RFC 7231 – Section 6.3.4 ]
; 204   No Content   [ RFC 7231 – Section 6.3.5 ]
; 205   Reset Content   [ RFC 7231 – Section 6.3.6 ]
; 206   Partial Content   [ RFC 7233 – Section 4-1 ]

; 3xx   Redirection
; 300   Multiple Choices   [ RFC 7231 – Section 6.4.1 ]
; 301   Moved Permanently   [ RFC 7231 – Section 6.4.2 ]
; 302   Found   [ RFC 7231 – Section 6.4.3 ]
; 303   See Other   [ RFC 7231 – Section 6.4.4 ]
; 304   Not Modified   [ RFC 7232 – Section 4.1 ]
; 305   Use Proxy   [ RFC 7231 – Section 6.4.5 ]
; 306   (Unused)   [ RFC 7231 – Section 6.4.6 ]
; 307   Temporary Redirect   [ RFC 7231 – Section 6.4.7 ]

; 4xx   Client Error
; 400   Bad Request   [ RFC 7231 – Section 6.5.1 ]
; 401   Unauthorized   [ RFC 7235 – Section 3.1 ]
; 402   Payment Required   [ RFC 7231 – Section 6.5.2 ]
; 403   Forbidden   [ RFC 7231 – Section 6.5.3 ]
; 404   Not Found   [ RFC 7231 – Section 6.5.4 ]
; 405   Method Not Allowed   [ RFC 7231 – Section 6.5.5 ]
; 406   Not Acceptable   [ RFC 7231 – Section 6.5.6 ]
; 407   Proxy Authentication Required   [ RFC 7235 – Section 3.2 ]
; 408   Request Timeout   [ RFC 7231 – Section 6.5.7 ]
; 409   Conflict   [ RFC 7231 – Section 6.5.8 ]
; 410   Gone   [ RFC 7231 – Section 6.5.9 ]
; 411   Length Required   [ RFC 7231 – Section 6.5.10 ]
; 412   Precondition Failed   [ RFC 7232 – Section 4.2 ]
; 413   Payload Too Large   [ RFC 7231 – Section 6.5.11 ]
; 414   URI Too Long   [ RFC 7231 – Section 6.5.12 ]
; 415   Unsupported Media Type   [ RFC 7231 – Section 6.5.13 ]
; 416   Range Not Satisfiable   [ RFC 7233 – Section 4.4 ]
; 417   Expectation Failed   [ RFC 7231 – Section 6.5.14 ]
; 426   Upgrade Required   [ RFC 7231 – Section 6.5.15 ]

; 5xx   Server Error
; 500   Internal Server Error   [ RFC 7231 – Section 6.6.1 ]
; 501   Not Implemented   [ RFC 7231 – Section 6.6.2 ]
; 502   Bad Gateway   [ RFC 7231 – Section 6.6.3 ]
; 503   Service Unavailable   [ RFC 7231 – Section 6.6.4 ]
; 504   Gateway Timeout   [ RFC 7231 – Section 6.6.5 ]
; 505   HTTP Version Not Supported   [ RFC 7231 – Section 6.6.6 ]