In article news:(E-Mail Removed),
(E-Mail Removed) wrote:
> Thanks for the reply Joerg, it is a public server and I'm not going
> through any proxies so it is strange, its also strange that it only
> happens randomly but quiet frequently, around 50% of the time, some
> sample code that calls the page in question is
>
Seems to work ok always for me, at least I've not repro'd any error in
the number of times that I've run it... Maybe someone else will find
different. There's no chance there's a transparent proxy in your path,
see if there's an Via header in the response for instance.
If you've a sniffer trace of case where it fails can you upload that
somewhere and we can have a look to see if there's something obviously
wrong with the response.
The format of chunked is relatively simple { n n n CR LF {data of size
nnn} CR LF } for each chunk, with the end marked with a zero length
chunk, and the length 'nnn' is an ascii formatted number
so the first trace I have has this response:
HTTP/1.1 200 ....
....
Flags: ... BRefresh=onCRLF
CRLF
65CRLF
{65 bytes of content}CRLF
289CRLF
{289 bytes of content}CRLF
0CRLF
CRLF
Seems ok -- should do as it was a successful download. (Not too sure
about the very last CRLF, but...)
--
Alan J. McFarlane
http://www.alanjmcf.me.uk/
Please follow-up in the newsgroup for the benefit of all.