\nI look at the start of the URL, grab every character to the end of the URL, making sure the last one isn’t a slash already, then rewrite that with slashes around it, issuing a 301 redirect and informing Apache not to process any more rules.\n<\/p>\n
\nThis works great for pages already on the server, for example \nOK, so we need not to match every character in the URL, but only if it doesn’t have a dot in there. The site in question was a Zend Framework application, and this caused it’s own problems.\n<\/p>\n \nZend Framework applications have their own rewriting rules…\n<\/p>\n \nThis checks if the requested resource is actually a real object Apache can serve, if not it passes it over to the Zend Framework to handle internally via the index.php script.\n<\/p>\n \nSo what happens if \nWell, the URL would be rewritten to \nWhy? Well the first rewrite we added a slash, this caused the page to re-requested, this then passed to the Zend Framework rewrites, this saw it needed to rewrite to index.php, this caused the page to be re-requested again internally, which added a slash to the end, and redirected again. Finally this request was \/index.php\/ which doesn’t exist and failed.\n<\/p>\n \nWow, that was a mouthful, let’s look at that as a sequence diagram.\n<\/p>\n \n \nWhat we need is to only rewrite the requested URL if it doesn’t have a trailing slash and if it doesn’t have a dot in the request and if it isn’t an internal Apache redirect. We also only want to rewrite if the request is a GET, POSTs (DELETE’s and PUT’s too) don’t support rewriting in the browser.\n<\/p>\n \nThis indicates a series a conditions that need to be met, so tells me we should be using Apache’s \nLet’s check for a GET request first…\n<\/p>\n \nThe \nNext we need to see if the request already has a trailing slash.\n<\/p>\n \nThis checks the requested URI and sees if the last character isn’t a slash.\n<\/p>\n \nNow we need to check if there are any dots in the request.\n<\/p>\n \nThis just checks that there isn’t a dot in the requested URI. As dot normally matches any character, we need to escape this with a clash first.\n<\/p>\n \nIf all these conditions match, we can issue our RewriteRule.\n<\/p>\n\/guestbook<\/code> becomes \/guestbook\/<\/code>. However, what if we wanted to load \/logo.gif<\/code>, this would rewrite to \/logo.gif\/<\/code> and cause a error.\n<\/p>\nRewriteCond %{REQUEST_FILENAME} -s [OR]\nRewriteCond %{REQUEST_FILENAME} -l [OR]\nRewriteCond %{REQUEST_FILENAME} -d\nRewriteRule ^.*$ - [NC,L]\nRewriteRule ^.*$ index.php [NC,L]\n<\/pre>\n\/guestbook<\/code> is actually a Zend Framework application?\n<\/p>\n\/index.php\/<\/code>.\n<\/p>\n![\"sequence](\"\/robblog\/images\/rewritesequence1.png\")
\n<\/p>\nRewriteCond<\/code> directive.\n<\/p>\nRewriteCond %{REQUEST_METHOD} GET [NC]\n<\/pre>\n%{REQUEST_METHOD}<\/code> variable in a rewrite rule tells us the HTTP method used to make the request, so we just need to check if that is GET. The [NC]<\/code> makes the check case insensitive so matches GET, get, Get, etc…\n<\/p>\nRewriteCond %{REQUEST_URI} !\/$\n<\/pre>\nRewriteCond %{REQUEST_URI} !.\n<\/pre>\nRewriteRule ^.*$ %{REQUEST_URI}\/ [R=301,L]\n<\/pre>\n
![\"sequence](\"\/robblog\/images\/rewritesequence2.png\")
<\/p>\n","protected":false},"excerpt":{"rendered":"