Posted by Michael Placentra II on 04/24/07 21:15

Steve wrote:
> "Jerry Stuckle" <jstucklex@attglobal.net> wrote in message
> news:PI-dnRTMkqyBw7TbnZ2dnUVZ_qvinZ2d@comcast.com...
> | 2good2b@gmail.com wrote:
> | > Hi,
> | > How can I differentiate between regular content and gzipped content on
> | > websites?
> | > Are there any other kinds of contents I should refer to? (I'm talking
> | > about websites-not applications)
> | > I would appreciate any ref.
> | > Thanks,
> | >
> |
> | I guess I don't understand your question. In what context are you
> | trying to differentiate?
>
> he's probably speaking of web sites that try to increase content transfer to
> the browser by zipping it. once the browser gets it, it unzips and presents
> the content in normal fashion. this is commonly done with gz_out
> functionality in php. however here, he wants to get the content rather than
> give. in either case, the headers in the client side let the server know
> whether or not zipped content is supported. therein lies his answer.
>
> as far as i can tell.


I think he means he wants to know whether or not the content on a page is gzipped. The easiest way to do that is to read the response headers from the server. If you use Firefox (2), you can just right click and click "View page info", then go to the headers tab. Look at Content-Encoding under response headers. Accept-Encoding under request headers is what Steve mentioned, and you can disable or change that through a Mozilla extension called Modify Headers (works on both SeaMonkey and Firefox):
https://addons.mozilla.org/en-US/firefox/addon/967

-Mike PII

[Back to original message]