@jeffkaufman , we've checked the per server configuration, we hit a snag there.
We cannot safely determine if we are in the root config or in a server config. Because all config is read in order. So a rollback per server with http as a root is almost undoable, we are introducing edge cases in which the configuration will be somewhat unpredictable (like http config lines between servers)

We now have 2 options:
- all configuration rollback if we see any gzip configuration
- per node rollback if we see gzip configuration on the same configuration node (this might be dangerous for existing configurations)

Adding to that we can add a pagespeed gzip force directive, this will force the gzip settings which we deem best for operation with pagespeed. Rethinking that we could use pagespeed gzip on/off for that, because nobody uses pagespeed gzip at this moment.

What do you think would be the way to go now?