HTTP Request\Response Header Grammer -

HTTP Request\Response Header Grammer -

in header of http request or response header keys constant in terms of capitalization, between servers.

i inquire can expect in code: (using false function names)

safe precise python code for hdr in header.keys(): if 'content-length' == hdr.lower(): recv_more_data( header[hdr] ) # header[hdr] == content-length (5388) bytes break # exit loop when if statement met. code use recv_more_data (header['content-length']) # know expect 'content-length' not 'content-length' or other variation

meaning server ever homecoming header keys so.

standard request get / http/1.1 host: www.example-host.com user-agent: mozilla/5.0 (windows nt 6.2; wow64; rv:33.0) gecko/20100101 firefox/33.0 accept: */* accept-language: en-us accept-encoding: gzip connection: closed content-length: 0 a bad possible response? http/1.1 200 ok server: nginx/1.0.15 date: thu, 23 oct 2014 00:25:37 gmt content-type: text/html; charset=iso-8859-1 transfer-encoding: chunked connection: close expires: thu, 19 nov 1981 08:52:00 gmt cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 pragma: no-cache content-encoding: gzip

clarification help code neatness.

http header names case-insensitive, per http specification.

rfc 2616 - hypertext transfer protocol -- http/1.1 section 4.2 - message headers

http header fields, include general-header (section 4.5), request-header (section 5.3), response-header (section 6.2), , entity-header (section 7.1) fields, follow same generic format given in section 3.1 of rfc 822 [9]. each header field consists of name followed colon (":") , field value. field names case-insensitive. field value may preceded amount of lws, though single sp preferred. header fields can extended on multiple lines preceding each line @ to the lowest degree 1 sp or ht. applications ought follow "common form", 1 known or indicated, when generating http constructs, since there might exist implementations fail take beyond mutual forms.

rfc 7230 - hypertext transfer protocol (http/1.1): message syntax , routing section 3.2 - header fields:

each header field consists of case-insensitive field name followed colon (":"), optional leading whitespace, field value, , optional trailing whitespace.

http http-headers httprequest httpresponse