Fixes #3591: implements automatic compression of deployed HTML, JS and CSS files#3592
Merged
mbarto merged 1 commit intogeosolutions-it:masterfrom Mar 6, 2019
Merged
Conversation
…yed HTML, JS and CSS files
Member
|
@tdipisa should be port this changes to the dependent projects, as well as the fix to pdf dependency issues?. If so, please remember to open an issue or integrate the extisting one in the related projects |
offtherailz
approved these changes
Mar 4, 2019
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Automatic compression of static files (JS, css, HTML, etc.) in deployed war/binary
Issues
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
What is the current behavior? (You can also link to an open issue here)
(gzip) compression of static files need additional configuration on the java web container or frontend (apache http, etc.). We could implement compression using a standard java filter to avoid additional configuration needs.
What is the new behavior?
Automatic compression of static files (JS, css, HTML, etc.) in deployed war/binary
Does this PR introduce a breaking change? (check one with "x", remove the other)
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: