caching and compression on same response

I am thinking about writing an i-rule to selectively configure caching and compression. Do I need to worry about whether the browser client will accept compression? For example, if the client is using HTTP 1.0 and doesn't claim to support compression, but I use the COMPRESS:enable, will the client get compressed content that they aren't expecting?

 

 

Also, is data compressed before it is cached or after is pulled from the cache? Do I need to worry about compressed content being pulled out of the cache and provided to a client that doesn't want compressed content?

 

 

We previously had compression enabled via a profile and had to disable it because certain users that accessed the site through a proxy (via HTTP 1.0) seemed to be getting compressed content and not knowing how to deal with it. If they used HTTP 1.1 through the proxy they were OK. I wasn't able to confirm, but my theory is that a downstream proxy was cacheing compressed content from our site and serving it up to HTTP 1.0 clients that weren't expecting it.

 

 

Do I just need to use a Cache-control: private header to prevent other proxies from caching things downstream?

 

 

We are using 9.2.2.

 

 

Thanks, Hal