Compression policy in POPs

Attach a protected object policy or POP to an object so that WebSEAL disables compression of that object.

We can specify a compression policy of do not compress in a POP. To specify this policy, add the following attribute to the POP:

document-compression = no

A POP without this attribute set, or with this attribute set to any value other than no, allows documents to be compressed.

The following example shows how to disable compression for the junction /appOne.

pdadmin> pop create appOnePop
pdadmin> pop modify appOnePop set attribute document-compression no
pdadmin> pop attach /WebSEAL/host/appOne appOnePop

To allow compression for a subdirectory beneath /appOne with an overriding POP, attach a different POP that does not have the document-compression attribute. For example:

pdadmin> pop create dataPop
pdadmin> pop attach /WebSEAL/host/appOne/data dataPop

This method of applying compression policy can be used with URLs. For example, to disable compression based on wildcard patterns applied to URLs, we can use dynurl. To disable compression for all requests to a junction that have a particular argument in the query string, we can create a dynurl.conf file with the following entries.

/disableCompression     /appOne/*\?want-response=text/xml

We can then attach a POP to /WebSEAL/host/disableCompression with the document-compression attribute set to no.

Parent topic: HTTP data compression