Quote:
|
Originally Posted by omerbutt how to use gzip in IIS all the info given there on yahoo is about APACHE but i am using IIS
Omer |
I have to agree. The 'FAQ spammers' seem not to have read the very pages to which they link. The question isn't how to zip a file. The question is how to get IIS to serve a zipped file so that the browser will reflate/expand it.
People have to think about what that means. It means that the browser is sending a request not for a file with a zip extension, or gz extension, or whatever, but with a .
js extension, say, for javascript. And IIS is supposed to route that request to a pre-zipped version of that javascript, which the site owner has separately uploaded, and send it back to the browser with the same suffix, .
js. That way, the browser will use its own routine to decompress the file and load it as a normal javascript. But far fewer bytes will have been sent than if it hadn't been compressed, is all. And that's a lot that has to happen. And I don't know of any 'FAQ' that can handle such questions.
In Apache, it's easy. Set .htaccess. All is well. Decompression occurs at the server. And redirects are possible, as well, to a pre-zipped file. But IIS seems more designed as a desktop OS, where it's just assumed everyone would have administrator privileges. Because I get the impression that in order to either a) compress at the server or b) route to a precompressed version of the file, that access to popup command consoles is required. And on shared servers, Microsoft doesn't seem to understand that a) those running the service may be clueless and b) those paying for shared hosting have no access to those control panels.
I do use server-side compression with Apache. I haven't tried with my IIS sites, obviously. But I wonder if on a file by file basis, which is much more limited, that one couldn't get around IIS restrictions using PHP? Many shared hosting services provide both ASP and PHP on their Microsoft servers.