1 <p>If you used page caching in a site that implements RESTful interface, you may face a problem. You could have multiple actions that share a single URL with different HTTP methods. For example, showing a document is served at /documents/1, while updating the same document is also at /documents/1. When I'm trying to update a document, the request is something like<br /> <br /> PUT /documents/1<br /> <br /> If your Apache is not well configured, it may respond with a cached file at /documents/1.html. This is wrong because this file should be served for GET requests only. In fact, POST, PUT and DELETE actions should never be cached because they change server state. Investigating in this issue, I found the following snippet at my .htaccess file.</p> <p>===================READ MORE===================</p> <p>&nbsp;&nbsp;&nbsp; # Conditions for fastcgi<br /> &nbsp;&nbsp;&nbsp; RewriteRule ^$ index.html [QSA]<br /> &nbsp;&nbsp;&nbsp; RewriteRule ^([^.]+)$ $1.html [QSA]<br /> &nbsp;&nbsp;&nbsp; RewriteCond %{REQUEST_FILENAME} !-f<br /> &nbsp;&nbsp;&nbsp; RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]<br /> <br /> To solve this problem I changed a line and added a new line to make it like this<br /> <br /> &nbsp;&nbsp;&nbsp; # Conditions for fastcgi<br /> &nbsp;&nbsp;&nbsp; RewriteRule ^$ index.html [QSA]<br /> &nbsp;&nbsp;&nbsp; RewriteRule ^([^.]+)$ $1.html [QSA]<br /> &nbsp;&nbsp;&nbsp; RewriteCond %{REQUEST_FILENAME} !-f<strong> <span style="color: rgb(51, 153, 102);">[OR]<br /> &nbsp;&nbsp;&nbsp; RewriteCond %{THE_REQUEST} !^GET</span></strong><br /> &nbsp;&nbsp;&nbsp; RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]<br /> <br /> This allows a request to served from file system only when the request is a GET request. This resolved the problem.</p> 3 2010-02-03T08:49:38Z true 10 true 5 ruby, rails, apache, caching, htaccess 2010-02-14T12:02:42Z 2010/2/3/skipping-cache-for-post-actions-in-apache