D Jianu

Greenhorn
+ Follow
since Nov 01, 2013
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
1
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by D Jianu

Thanks a lot, this makes sense! Still not sure yet how to use IIS to minify .JSP files. Seems that all solutions are for .ASP pages. Any thoughts?

But thanks again for clarifying my previous question, that was very helpful.


Tim Holloway wrote:What is "minification"?

Do you mean data compression?

If so, it is hardly unexpected to see this problem. When Tomcat is in charge of transport, Tomcat can choose to compress data, based on configuration information and stated MIME types. But if Tomcat is being proxied by IIS, then it's the job of IIS to determine the compression (and encryption) of the data streams. The Tomcat-to-IIS data tunnel is not an open HTTP link and it isn't likely to be using the same protocols, but rather protocols more suitable for proxy transfers.

10 years ago
Hi,

Hope this is the right place to ask this question. I could not find an answer anywhere.

I have a website running on a server with Tomcat (port 8080) and IIS (6). I've implemented the webutilities filter from Google (to minify resource files) and added it to the web.xml file of my project (WEB-INF/web.xml).

When I access a resource-file (JS / CSS) on my website from a browser (through IIS), it shows that it was not minified. However, when I access it directly through Tomcat (port 8080) it shows up as minified.

This tells me that the filter I added in the web.xml file in fact works, but for some reason IIS or ISAPI must be somehow blocking the minification. Is this possible? Does anyone know if minification with Tomcat conflicts in any way or is being cancelled by IIS?

Any advice on how to fix this would be greatly appreciated. Thank you!
10 years ago