Custom response codes and content-types for memcache module
mdounin at mdounin.ru
Tue Jul 22 14:18:50 MSD 2008
On Tue, Jul 22, 2008 at 11:50:51AM +0200, M. Van der klip wrote:
>I have recently written a patch which allows storage of custom HTTP
>response codes and Content-type headers within memcache alongside the
>actual response body. This allows us to pass the not_found's of the
>memcache module to a PHP script which can serve and store different
>kinds of responses in the cache.
>The chosen approach is quite rough for this first version. The memcache
>module is able to interpret two special commands prepended to the
>This example serves a custom 404 page from memcached:
>^SET-STATUS:404 Not Found|<HTML><BODY>...
I don't think it's good idea to introduce brand-new format just
for this. Why not use plain http headers as proxy module does (or
http headers with CGI/1.1 directives as fastcgi does)? This
particular reply can be simplified to:
Status: 404 Not Found
>This example serves /sitemap.xml from memcached:
>^SET-CONTENT-TYPE:application/xml; charset=UTF8|<?xml version="1.0"
>Please let me know if there is any interest in this patch. If so, I
>could make it available. Without any warranties ofcourse. :P
>Posted via http://www.ruby-forum.com/.
More information about the nginx