No subject

code line and that's it. If the file exists you send the file, if not just
the response code. Whereas with HTTP/1.0 you send the additional headers.

is this right?

i.e. for HTTP 0.9

Client: GET /index.html

Server: HTTP/1.0 200 OK
<file contents>

----

Client: GET /index.html

Server: HTTP/1.0 404 Not Found

Or do we still send other things like Date/Server name/etc. back?

--001a11c36778d07a6f04ebec8580
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I&#39;ve been reading the RFC and I understand 0.9 are sim=
ple requests that only support GET and no content-types, etc.<div><br></div=
><div>However, how do you respond to HTTP 0.9 requests?</div><div><br></div=
>
<div>i.e. GET /index.html is a HTTP 0.9 request</div><div><br></div><div>Fr=
om the RFC it seems you don&#39;t respond with headers but just the respons=
e code line and that&#39;s it. If the file exists you send the file, if not=
 just the response code. Whereas with HTTP/1.0 you send the additional head=
ers.</div>
<div><br></div><div>is this right?</div><div><br></div><div>i.e. for HTTP 0=
.9</div><div><br></div><div>Client: GET /index.html</div><div><br></div><di=
v>Server: HTTP/1.0 200 OK<br></div><div>&lt;file contents&gt;</div><div>
<br></div><div>----</div><div><br></div><div>Client: GET /index.html</div><=
div><br></div><div>Server:=A0HTTP/1.0 404 Not Found</div><div><br></div><di=
v>Or do we still send other things like Date/Server name/etc. back?</div>
<div><br></div></div>

--001a11c36778d07a6f04ebec8580--