The com.sun.jersey.spi.container.ContainerResponseFilters feature is misleading when used in conjunction with FEATURE_FILTER_FORWARD_ON_404.
I spent almost an entire day trying to figure out why a unit test was getting HTTP 405 from a resource that returned HTTP 404. It turns out that FEATURE_FILTER_FORWARD_ON_404 was enabled and Grizzly returns HTTP 405 for unknown URLs (which seems a bug in its own right).
Here is what the server-side and client-side logs showed:
Expected behavior: Server-side code should indicate that FEATURE_FILTER_FORWARD_ON_404 caused the response to be forwarded to a subsequent servlet filter, and it should report the final response that comes out of it.