HTTP questions
Maarten Bezemer
I'm currently updating NetWatch and I'm having 1 small problem with the
HTTP protocol:
Pages which gets created by scripts don't have a Content-Length field.
So NetWatch doesn't know when the last bytes are received. I don't like
this very much so I've been looking with Nettle at such pages.
In the 'Open new session window'
I fill in host : www.drobe.co.uk:80 and I click on Connect
In the Nettle window I type:
GET / HTTP/1.1
Host: www.drobe.co.uk
Connection: close
The response is
HTTP/1.1 200 OK
<snip more header info>
Content-Type: text/html
eae
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<snip rest op document>
</body></html>
0
Nettle: Remote has closed the connection
Nettle: Disconnected
Now I see 2 strange things I can't explain:
What is the 'eae' after the header info? Can I use it for a document
size?
And the '0' after the document (assuming that this isn't a part of the
webpage)
I get almost the same with
http://www.stronged.iconbar.com/pages/download.html
The 'eae' becomes 'ef8' and the '0' is also there.
So I'd like to know what these values mean, so I may use them in
NetWatch.
Cheers,
Maarten
--
Maarten Bezemer
Ralph Corderoy
> I'm currently updating NetWatch and I'm having 1 small problem with
> the HTTP protocol:
You really need to read all of RFC2616, _Hypertext Transfer Protocol --
HTTP/1.1_, as NetWatch needs to cope with the many different replies it
may receive, not just the ones found in testing.
ftp://ftp.isi.edu/in-notes/rfc2616.txt
> The response is
>
> HTTP/1.1 200 OK
> <snip more header info>
You snipped `Transfer-Encoding: chunked' which is significant. See 4.4
of the RFC for determining message length, in particular 4.4.2.
> eae
This is `1*HEX'; the chunk-size. See 3.6.1.
> 0
See RFC2616. ;-)
Cheers,
--
Ralph Corderoy. http://inputplus.co.uk/ralph/ http://troff.org/
Maarten Bezemer
On 15 May 2003 "Ralph Corderoy" <ra...@inputplus.co.uk> wrote:
> Hi Maarten,
>
> > I'm currently updating NetWatch and I'm having 1 small problem with
> > the HTTP protocol:
>
> You really need to read all of RFC2616, _Hypertext Transfer Protocol --
> HTTP/1.1_, as NetWatch needs to cope with the many different replies it
> may receive, not just the ones found in testing.
>
> ftp://ftp.isi.edu/in-notes/rfc2616.txt
>
> > The response is
> >
> > HTTP/1.1 200 OK
> > <snip more header info>
>
> You snipped `Transfer-Encoding: chunked' which is significant. See 4.4
> of the RFC for determining message length, in particular 4.4.2.
>
> > eae
>
> This is `1*HEX'; the chunk-size. See 3.6.1.
>
> > 0
>
> See RFC2616. ;-)
I read it already it's on my harddisk, but I hadn't study all header
fields, because NetWatch won't need most of them.
So thanks for the hint on reading the complete document :-)
Justin Fletcher
> Hi,
>
> I'm currently updating NetWatch and I'm having 1 small problem with the
> HTTP protocol:
> Pages which gets created by scripts don't have a Content-Length field.
> So NetWatch doesn't know when the last bytes are received. I don't like
> this very much so I've been looking with Nettle at such pages.
>
> In the 'Open new session window'
> I fill in host : www.drobe.co.uk:80 and I click on Connect
>
> In the Nettle window I type:
> GET / HTTP/1.1
> Host: www.drobe.co.uk
> Connection: close
>
> The response is
>
> HTTP/1.1 200 OK
> <snip more header info>
> Content-Type: text/html
>
> eae
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
[snip]
> Now I see 2 strange things I can't explain:
> What is the 'eae' after the header info? Can I use it for a document
> size?
> And the '0' after the document (assuming that this isn't a part of the
> webpage)
Know thy HTTP specifications. You're asking for a HTTP 1.1 response.
That's what you got. RFC2616, 3.6 and more specifically 3.6.1.
--
Gerph {djf0-.3w6e2w2.226,6q6w2q2,2.3,2m4}
URL: http://www.movspclr.co.uk/
... In violent times, you shouldn't have to sell your soul.