I've merged your HttpProt changes into the latest version, and added
the LocationChangeMaxCount feature to prevent endless relocation looping.
The component is backward compatible, when option
httpoEnableContentCoding is not used, but does now need your
HttpContCod.pas unit to be added to the ICS distribution.
Using your HttpCCodGzip unit, while enabling compression adds the
correct header to the protocol, suggesting it's all linked OK,
unfortunately the HEAD request just gets a status of 0.
= Connected to: web4
> HEAD /dunman/default.asp HTTP/1.0
> Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
> Accept-Encoding: gzip
> User-Agent: Mozilla/4.0 (compatible; ICS)
> Host: web4
Can Not Access URL: http://web4/dunman/default.asp, (0)
I suspect that the encoding header should not be sent with the HEAD
request, I'll try and change the code tomorrow.
-------- Original Message --------
*Subject:* Re: [twsocket] HTTP compression
*From:* Maurizio Lotauro <[EMAIL PROTECTED]>
*To:* ICS support mailing <email@example.com>
*Date:* Tue, 22 Nov 2005 17:11:01 +0100
Scrive Angus Robertson - Magenta Systems Ltd <[EMAIL PROTECTED]>:
> I'm sure there are good reasons for all the work you did, I've just not
> yet found the demo application or readme. But I will at least try it
> later this week.
You must use the content of HttpContCod.zip that is in the ICS web page
the first in the list of beta). Probably it is not in sync with latest
but for evaluation it should not matter.
To test it you can use the standard HttpTst demo. Uncompress the zip in
same dir and add HttpCCodGzip to the uses of one unit of the project. So
can test it without messing your ICS installation.
If you don't add HttpCCodGzip then the gzip encoding will not be used
component should work as usual.
The header of HttpContCod.pas contains a brief description.
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be