HTTP Response Headers

HTTP Response

Like Request, HTTP Response has three parts:
  • Status Line
  • Headers
  • Message Body
HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Content-Type: text/html;charset=ISO-8859-1 Transfer-Encoding: chunked Date: Tue, 17 Jul 2012 20:43:18 GMT

CREATED 2012-07-17 12:52:51.0


UPDATED 2012-09-10 14:26:11.0

Status Line...

The Status Line indicates what happened. It is made up of three parts...

  • HTTP Version
  • Status Code
  • Reason Phrase - a description of the Status Code

There are a bunch of Status Codes that all fall into basically 4 groups

  • 2xx (200-299) indicates a success. That means it worked. The different codes indicate specifics (accepted/created/partial content/...) but any 200 code is good.
  • 3xx (300-399) indicates redirection. Means the resource requested has been moved, deleted or not modified. e.g. 304 Notmodified is is returned if the browser was refreshed and the page didn't change.
  • 4xx (400-499) means the client has a problem. Bad Request, Can't do it, unathorized, etc.
  • 5xx (500-599) indicates the server had a problem servicing the request.

CREATED 2012-07-17 12:55:57.0


UPDATED 2012-09-10 14:26:06.0


Here is a complete list of HTTP Response Header Fields. Also WIKIPedia has a good write up on HTTP Header Fields for both request and response.

CREATED 2012-07-17 13:01:12.0


UPDATED 2012-09-10 14:26:12.0

The Blank Line...

There has to be a blank line, that is 2 line feed/carrage return combos between the header and the payload in both the request and response messages.

CREATED 2012-09-10 14:36:04.0


UPDATED 2012-09-10 14:37:48.0

Message Body...

The message body or the payload is the response from the server. The meat and potatoes. The Jack Pot. It's what the client asked for.

CREATED 2012-07-17 13:01:44.0


UPDATED 2012-09-10 14:26:14.0



DBID: db.wam

Page Server: Ruger

©2012 Leistware Data Systems

      Hello anonymous