Comments on: Apache HTTP encoding negotiation notes http://www.mrclay.org/2008/05/25/apache-http-encoding-negotiation-notes/ Steve Clay on programming, music, public policy and other junk Tue, 17 Apr 2012 07:00:30 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Gilles http://www.mrclay.org/2008/05/25/apache-http-encoding-negotiation-notes/comment-page-1/#comment-102214 Gilles Tue, 28 Jul 2009 09:39:21 +0000 http://mrclay.org/?p=200#comment-102214 Hi Steve, You said in project goal #3: "Minify should work towards maintaining builds of pre-encoded files and letting Apache serve them." Will this work? - Dynamic CMS which knows which JS files to include (e.g. thesame as "/?f=..." - Get the last modified date - Create an MD5 hash of these files (to get the filename) - Append the lastmod date so you get -12345.js - Use Minify to create this file - Use typemap so apache serves the correct file to the browser. All i am wondering is how Apache will handle the caching, since you no longer go through the PHP interperter. Any ideas / tests on this one? Hi Steve,

You said in project goal #3:
“Minify should work towards maintaining builds of pre-encoded files and letting Apache serve them.”

Will this work?
- Dynamic CMS which knows which JS files to include (e.g. thesame as “/?f=…”
- Get the last modified date
- Create an MD5 hash of these files (to get the filename)
- Append the lastmod date so you get -12345.js
- Use Minify to create this file
- Use typemap so apache serves the correct file to the browser.

All i am wondering is how Apache will handle the caching, since you no longer go through the PHP interperter. Any ideas / tests on this one?

]]> By: Tobias http://www.mrclay.org/2008/05/25/apache-http-encoding-negotiation-notes/comment-page-1/#comment-102193 Tobias Tue, 21 Jul 2009 13:52:14 +0000 http://mrclay.org/?p=200#comment-102193 It would be useful if you can configure Apache that it generates the different encodings just once when there do not exist the different file versions or the base file changed. So you don't have to manually compress them each time you upload/change a file. It would be useful if you can configure Apache that it generates the different encodings just once when there do not exist the different file versions or the base file changed. So you don’t have to manually compress them each time you upload/change a file.

]]> By: Steve http://www.mrclay.org/2008/05/25/apache-http-encoding-negotiation-notes/comment-page-1/#comment-97705 Steve Tue, 10 Jun 2008 20:26:41 +0000 http://mrclay.org/?p=200#comment-97705 @Peter: Thanks. The RewriteRule I gave is correct. It purposefully redirects to the un-encoded resource for the targeted browsers. So: IE5: GET file.js.var => file.js Only the non-buggy browser requests get handled by mod_negotiation. BTW, I've recently rewritten Minify::serve to get about 3x the performance. It's now faster than mod_deflate! @Peter: Thanks. The RewriteRule I gave is correct. It purposefully redirects to the un-encoded resource for the targeted browsers. So:

IE5: GET file.js.var => file.js

Only the non-buggy browser requests get handled by mod_negotiation.

BTW, I’ve recently rewritten Minify::serve to get about 3x the performance. It’s now faster than mod_deflate!

]]> By: Peter Bowey http://www.mrclay.org/2008/05/25/apache-http-encoding-negotiation-notes/comment-page-1/#comment-97702 Peter Bowey Tue, 10 Jun 2008 14:30:45 +0000 http://mrclay.org/?p=200#comment-97702 Update: Mention to your readers that the above .htaccess directive file is to be placed in its respective static resource folder (eg: <b>/css</b> or <b>/javascript</b>) and not the <b>root folder</b>. Also you could explain the value of the <code>RewriteBase /tests/encoding-negotiation</code>. This is the /path to the static resource (css or javascript). On my own live website, I have implemented a <b>HTTP encoding negotiation</b> method with <b>type-map</b> resources (javascript and css) and it works very well. I have also tried 'minify' code and benchmarked the 'real-time' results as marginal compared to the <b>“Apache HTTP encoding negotiation notes”</b> pre-compression technique. Thanks for sharing! We learn from each other, your project and notes have helped me heaps! Update: Mention to your readers that the above .htaccess directive file is to be placed in its respective static resource folder (eg: /css or /javascript) and not the root folder. Also you could explain the value of the RewriteBase /tests/encoding-negotiation. This is the /path to the static resource (css or javascript).

On my own live website, I have implemented a HTTP encoding negotiation method with type-map resources (javascript and css) and it works very well. I have also tried ‘minify’ code and benchmarked the ‘real-time’ results as marginal compared to the “Apache HTTP encoding negotiation notes” pre-compression technique.

Thanks for sharing! We learn from each other, your project and notes have helped me heaps!

]]> By: Peter Bowey http://www.mrclay.org/2008/05/25/apache-http-encoding-negotiation-notes/comment-page-1/#comment-97700 Peter Bowey Tue, 10 Jun 2008 14:03:05 +0000 http://mrclay.org/?p=200#comment-97700 Update Correction: The Apache buggy browser code (last line) needs changing from (orig) RewriteRule ^(.*)\.var$ $1 [L] // fixed and tested on both IE6 with SV1 and IE6 without to RewriteRule ^(.*)\.css$ $1 [L] or RewriteRule ^(.*)\.js$ $1 [L] Update Correction:

The Apache buggy browser code (last line) needs changing from

(orig) RewriteRule ^(.*)\.var$ $1 [L]
// fixed and tested on both IE6 with SV1 and IE6 without
to RewriteRule ^(.*)\.css$ $1 [L]
or RewriteRule ^(.*)\.js$ $1 [L]

]]> By: Steve http://www.mrclay.org/2008/05/25/apache-http-encoding-negotiation-notes/comment-page-1/#comment-97338 Steve Wed, 04 Jun 2008 03:51:47 +0000 http://mrclay.org/?p=200#comment-97338 Update: The configuration above can <a href="/index.php/2008/06/03/pre-encoding-vs-mod_deflate/" rel="nofollow">serve larger files 2.5x as fast as using mod_deflate</a>. Update: The configuration above can serve larger files 2.5x as fast as using mod_deflate.

]]>