GzipFilter and Jersey with FEATURE_FILTER_FORWARD_ON_404 are not compatible

I am trying to speed up the loading of some large web pages for the Hadoop project. One of the issues that I am running into is that Hadoop also uses Jersey to supply web services, and uses FEATURE_FILTER_FORWARD_ON_404 in Jersey as part of this.

What this feature does is that Jersey will first try to see if any class is registered to handle a request, if not it will set the status code to 404. A Jersey filter further up the stack sees the 404 status, resets the status to 200 and then tries sending the request through to the rest of the configured filters/servlets.

The problem that I am running into is that GZipFilter disables compression for that request the moment that it see the 404 status code, even though it is going to be set back to 200 later on.