Gzip at runtime and minify/build/compile at build

[alexo]

Gzip at runtime and minify/build/compile at build

[FagnerMartinsBrack]

Well... After many tries I could not find a way to disable minification from the filter feature through any option and keep only gzip, thoughts?

[alexo]

Hi,
the less + minify + concatenation is supported by maven plugin by default. For gzip, you can create a simple Filter or reuse one from existing libraries which just gzip the response, or let the container handle the gzip.

[FagnerMartinsBrack]

Any possibility to do and document something like this as a feature? That would be just gzip through wro4j...

[alexo]

Ok, I'll add a dedicated filter which will handle the gzip operation.

[FagnerMartinsBrack]

@alexo
Any news on this?

[alexo]

@FagnerMartinsBrack Didn't have time for that. But will mark it as high priority for the next release.

[alexo]

@FagnerMartinsBrack just to make sure I understand the requirement correctly:

A new filter will be created which will focus on handling gzip response content only. Is that correct?

[FagnerMartinsBrack]

Yes. I could be using minify and concat at build, but as far as I know gzip can only be issued at runtime (so I miss gzip when using the build feature).

It would be very nice if you could gzip HTML too -.-, unless you wanna wait for #104 conclusion.

[alexo]

The filter will be applied to all resources mapped by the filter. So, it will be client responsibility to define correct mapping (the same way WroFilter is configured).

[FagnerMartinsBrack]

Oh, ok. So I map the resources according to the filter, understood.

[alexo]

Actually I am trying to clarify the requirements.

[FagnerMartinsBrack]

The main requirement is:

• GZIP any resource without using the other features such as concat/minify/etc at runtime.

If it is possible we could gzip the HTML too (I am not sure if your idea is to specify file extensions in the filter also or only the path that will be looked for).

I have almost no experience in Servlet filters, so I could be making assumptions that are not possible (like some web.xml limitation).

[alexo]

A filter handling gzipping allows flexible customization either using filter-mapping (in web.xml) or extending the filter (programmatic configuration). I don't see a better solution for this. Let me know if you have other suggestions.

[FagnerMartinsBrack]

I think that is the way to go.

[alexo]

Fixed in branch 1.6.x

[FagnerMartinsBrack]

Hi, thanks for the implementation. Is there any docs yet?

[alexo]

I'll add some docs later, just before the final 1.6.4 release will be available. It should be quite straightforward how to use it - just as it was described earlier in comments of this issue.

[FagnerMartinsBrack]

Ok