http://WellFormedWeb.org/news/24 <p>That is to say that all the URLs on this site are cool, with cool being defined by Tim Berners-Lee in his article <a href="http://www.w3.org/Provider/Style/URI.html">Cool URIs don't change</a>. In the article he argues that URLs should never change and the best way to achieve that is to do some up front design of your URLs so that you won't need to change them in the future.</p> <p>The URLs for the weblog entries on this site used to be of the form:</p> <pre class="example"><code>http://WellFormedWeb.org/RESTLog.cgi/1</code></pre> <p> In the article Tim Bernes-Lee gives a list of things to leave out of your cool URL. Now my URLs were mostly cool because they didn't include such information as the authors name, the subject, the status, or the file name extension. The only information embedded in that URL is the software mechanism: .cgi. It has to go. If a new and better method comes along to server up my content and I deploy it then I end up breaking my URLs, and that's not cool. So I need a way to remove any reference to .cgi and also allow the old URLs which are already linked to out in the wild of the internet to keep working. The server I am running on requires the use of the .cgi extension so just renaming the file won't work.</p> <h3>Apache to the rescue</h3> <p>The Apache module <a href="http://httpd.apache.org/docs/mod/mod_rewrite.html">mod_rewrite</a> comes to the rescue. This powerful module allows rewriting of URLs on the fly. So I have two ugly URLs to contend with, <code>/RESTLog.cgi</code> and <code>/stories/RESTLog.cgi</code>. The first I want mapped to <code>/news</code> and the second I want mapped to <code>/story</code>. Here is the section of my .htaccess file that accomplishes that rewriting: </p> <pre class="example"><code>RewriteEngine on RewriteBase / RewriteRule ^news(.*) /RESTLog.cgi$1 [L] RewriteRule ^story(.*) /stories/RESTLog.cgi$1 [L] </code></pre> <p>Note that these rules only modify a URI if they start with "news" or "story" so the old URIs will still work even after I switch to using the new URLs. Which means no broken links. Now that's cool. </p> <p>This change also required some changes on the server side code. The code was extended by adding a <code>base_uri__</code> variable to RESTLogImpl.py that is used as the base URI for all urls generated. This fixes a problem when accessing the web site and ModRewrite is in use. SCRIPT_NAME used to be used to generate the urls which was easy to do but if not robust. For example I want all the URLs on WellFormedWeb to be of the form:</p> <pre class="example"><code>http://WellFormedWeb.org/news/N</code></pre> <p>but the server is only configured to execute scripts if the filename ends in .cgi so I am stuck with:</p> <pre class="example"><code>http://WellFormedWeb.org/RESTLog.cgi/N</code></pre> <p>I can use ModRewrite to accept <code>/news</code>:</p> <pre class="example"><code>RewriteEngine on RewriteBase /cgi-bin/ RewriteRule ^cgi-bin/news(.*) /cgi-bin/RESTLog.cgi$1 [L]</code></pre> <p>But even with this rewrite in place the SCRIPT_NAME still points to RESTLog.cgi and the permalinks generated have RESTLog.cgi in them and not news. So the answer I came up with is to set it in the main script <code>RESTLog.cgi</code>. The alternative was to look for some other potentially missing cgi environment variables that are present if a rewrite was done, but then I realized that created a whole new problem: If I had two installs of pamphlet and they were configured differently, one for <code>/RESTLog.cgi</code> and the other for <code>/news</code> then posts from each install would have a different form of the permalink. Yuk. </p> <p>Postscript: Much thanks to <a href="http://diveintomark.org">Mark Pilgrim</a> for sending me some of his .htaccess files as examples and pointing me to <a href="http://www.engelschall.com/pw/apache/rewriteguide/">A Users Guide to URL Rewriting with the Apache Webserver</a> which is also loaded with examples.</p> BitWorking, Inc