foo.jar. pac k.gz
AE=”pack200-gzip, gzip’
Requests foo.jar
foo.jar
Sends foo.jar.pack.gz <-
CE=”pack200-gzip” CT=”application/java-archive
Example 1: Application reąuesting packed or compressed jar
foo.jar. pac k.gz
AE=”pack200-gzip, gzip’
foo.jar.gz
In the above example, the client reąuests a file foo.jar with AE="pack200-gzip, gzip", the server will search for the file f oo . j ar. pack. gz and send it and will set CE to
pack200-gzip.
foo.jar
Sends foo.pack.gz ◄-
pCE=”pack200-gzip” CT=”application/java-archive
foo.jar.gz
Example 2: Application reąuesting packed or compressed jar
In the above example, if f oo .jar. pack. gz is not found, the server will respond back with f oo .jar. gz, if found, and the CE will be set to gzip.
Reąuests foo.jar
foo.jar
Sends foo.pack.gz <-
CE=”pack200-gzip” CT=”application/j ava-archive
Example 3: Application reąuesting packed or compressed jar
AE=”pack200-gzip, gzip”
In the above example, if f oo .jar. pack. gz and f oo . j ar. gz is not found then the server will respond back with f oo . j ar and the CE will not be set or set to NULL.
In the above example, a legacy application (application without HTTP or Pack200 compression) reąuests f oo. j ar, and will continue to work seamlessly. Therefore it is recommended all the files f oo. j ar, foo. j ar. gz and f oo .jar. pack. gz be hosted..