W3C home > Mailing lists > Public > www-talk@w3.org > January to February 2000

Re: quickie: client force no headers in server response

From: Christian Bhn <chrb@online.no>
Date: Wed, 9 Feb 2000 21:17:07 +0100
Message-ID: <000001bf738c$b5791410$b80a4382@bohns>
To: "Davin" <s2207754@cse.unsw.edu.au>, <www-talk@w3.org>
No. But when you receive a double CRLF the header is finished, there is no
other ways that I know of. To find out what content it is, check out the
Content-Type: header.

Christian


> Guys, is there anyway I can force the server to not send the HTTP header.
> I know you can use HEAD to get the headers, but is there a reverse of HEAD
> to receive only the entity.
>
> My program simply calls socket() to port 80 of a server.Then write() "GET
> <url>", block on read() and pending the server implementation I receive
> the header or not. Is there a way I can force it to simply send the
> entity, so I'm guaranteed to receive the body, no matter what
> implementation server I'm connecting to.
>
> There's a kludge I could do, and that is, the RFC states that the header
> and entity should be separated by a CRLF, but thats too dirty to program
> for, especially when you don't know when servers send the header of not. I
> have to keep in mind that I cannot assume what the response format may be,
> ie text, gif, etc..
>
> Anyone found themselves in this situation before?
> Thanks,
> Davin.
>
Received on Thursday, 10 February 2000 01:03:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 October 2010 18:14:24 GMT