Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I found this article http://archive.webproasp.com/webproasp-27-20080620CompressingWebResourceaxdtoReduceYourWebsiteSize.html
and it explains how to compress axd files (and js files).
I wondered if there is any advantage in doing this over letting IIS handle the compression.
Users on shared hosting often aren’t able to change the compression settings on IIS. Using http handlers allows this to be done from within the application.
If you can setup compression at the IIS level there is no reason not to.