HTTP response/ obligatorske headere ?

Hvad der er optional og hvad der er mandatory afhaenger saa vidt jeg ved af om det er HTTP 1.0 eller 1.1.

Men i begge tilfaelde boer det fremgaa af RFC'en om en header er optional eller mandatory.

http://www.ietf.org/rfc/rfc1945.txt
http://www.ietf.org/rfc/rfc2616.txt

Jeg har været igennem RFC'en - dog ikke med lup :) - og har ikke umiddelbart fundet nogle headere, der er obligatoriske, så ud fra det, så skulle min løsning jo overholde protokollen.

Skulle der være en, der kan se, at der er fejl i det jeg har lavet, så vil jeg meget gerne have en tilbagemelding.

Hilsen
Brian

Der står f.eks.:

A client MUST include a Host header field in all HTTP/1.1 request
  messages

hvilket dækker over at requests med HTTP 1.1 som protokol skal inkludere en Host header. Hvilket er klassisk.

Jeg kan ikke umiddelbart huske nogen for response, men lidt søgning finder:

If no response body is included, the
  response MUST include a Content-Length field with a field-value of
  "0".

...

10.3.5 304 Not Modified

  If the client has performed a conditional GET request and access is
  allowed, but the document has not been modified, the server SHOULD
  respond with this status code. The 304 response MUST NOT contain a
  message-body, and thus is always terminated by the first empty line
  after the header fields.

  The response MUST include the following header fields:

      - Date, unless its omission is required by section 14.18.1

  If a clockless origin server obeys these rules, and proxies and
  clients add their own Date to any response received without one (as
  already specified by [RFC 2068], section 14.19), caches will operate
  correctly.

      - ETag and/or Content-Location, if the header would have been sent
        in a 200 response to the same request

      - Expires, Cache-Control, and/or Vary, if the field-value might
        differ from that sent in any previous response for the same
        variant

...

10.4.2 401 Unauthorized

  The request requires user authentication. The response MUST include a
  WWW-Authenticate header field (section 14.47) containing a challenge
  applicable to the requested resource.

...

10.4.6 405 Method Not Allowed

  The method specified in the Request-Line is not allowed for the
  resource identified by the Request-URI. The response MUST include an
  Allow header containing a list of valid methods for the requested
  resource.

...

  HTTP/1.1 defines the "close" connection option for the sender to
  signal that the connection will be closed after completion of the
  response. For example,

      Connection: close

  in either the request or the response header fields indicates that
  the connection SHOULD NOT be considered `persistent' (section 8.1)
  after the current request/response is complete.

  HTTP/1.1 applications that do not support persistent connections MUST
  include the "close" connection option in every message.

...

  If the content-coding of an entity is not "identity", then the
  response MUST include a Content-Encoding entity-header (section
  14.11) that lists the non-identity content-coding(s) used.

...

  Origin servers MUST include a Date header field in all responses,
  except in these cases:

      1. If the response status code is 100 (Continue) or 101 (Switching
        Protocols), the response MAY include a Date header field, at
        the server's option.

      2. If the response status code conveys a server error, e.g. 500
        (Internal Server Error) or 503 (Service Unavailable), and it is
        inconvenient or impossible to generate a valid Date.

      3. If the server does not have a clock that can provide a
        reasonable approximation of the current time, its responses
        MUST NOT include a Date header field. In this case, the rules
        in section 14.18.1 MUST be followed.

så lidt regler er der !

Connection close er nok den mest kritiske.

Hvis du snakker HTTP 1.0 er det lidt simplere.

all set ?