Re: AsyncHttp for Thomas Parslow
> Ok, let me ask this another way, because something is going on with the
> way the http is threaded thru the computer. When i access this url:
> http://abcnews.go.com/wire/World/ap20020519_573.html
> With Webshepard, i get 12,655 bytes of this:
> í}ùrÛFÖïßVUÞ <snip>
> With Asynchttp, i apparently get 45,336 bytes of this:
> <!-- Published on Sunday May 19, <snip>
> I changed nothing except the Eu program used to fetch the url. Obviously
> Asynchttp is decoding the page for me, but how? Or is it overriding the
> defaults of IE and specifying to the server that i want only plain clear text?
>
> Part of Async headers sent is ""Accept: */*\n"&" which tells me it will accept
>
> anything, includng the compressed version of the file. What is it using in
> windows to do this, and when? If i use the Webshepard (or any other http/tcp
> retriever), how would i decode that compressed file once i have it?
> Kat,
> puzzled
It's definitely not a case of AsyncHTTP decompressing the page, I
would remember coding that :)
It must be difference in the headers sent to the server, AsyncHTTP
sends a HTTP/1.1 and according to the HTTP standards it must
specifically specifically if it supports compression (which it
doesn't). Webshepard uses wininet and I'm not sure what headers that
sends (you could use a packet sniffer to find out)...
I tried a few different headers via telnet and none of them produced a
compressed respone...
Thomas Parslow (PatRat)
E-Mail/Jabber: tom at almostobsolete.net
ICQ: 26359483
|
Not Categorized, Please Help
|
|
