Comments on: lighttpd, Take 2 http://www.splee.co.uk/2005/11/17/lighttpd-take-2/ Bring out the g33k Thu, 20 Nov 2008 17:23:37 +0000 http://wordpress.org/?v=2.6 By: Splee http://www.splee.co.uk/2005/11/17/lighttpd-take-2/#comment-1206 Splee Thu, 12 Jan 2006 14:40:00 +0000 http://www.splee.co.uk/2005/11/17/lighttpd-take-2/#comment-1206 Yes, that's what I did originally. I didn't have any rewrite rules at all, I just set the 404 handler to: <code>server.error-handler-404 = "/index.php?error=404"</code> When I first set this up the server would always return a 404 response, even though it returned the right page as the body of the response. The upshot of that was that bots and a number of feed readers wouldn't retrieve anything as they just discarded the body once they saw the 404. Thankfully everything is working nicely now. :) Yes, that’s what I did originally. I didn’t have any rewrite rules at all, I just set the 404 handler to:

server.error-handler-404 = "/index.php?error=404"

When I first set this up the server would always return a 404 response, even though it returned the right page as the body of the response. The upshot of that was that bots and a number of feed readers wouldn’t retrieve anything as they just discarded the body once they saw the 404.

Thankfully everything is working nicely now. :)

]]> By: Cliff Wells http://www.splee.co.uk/2005/11/17/lighttpd-take-2/#comment-1205 Cliff Wells Thu, 12 Jan 2006 14:13:09 +0000 http://www.splee.co.uk/2005/11/17/lighttpd-take-2/#comment-1205 Perhaps setting the 404 handler in lighttpd.conf to point to index.php (or whatever it is that wordpress uses)? Perhaps setting the 404 handler in lighttpd.conf to point to index.php (or whatever it is that wordpress uses)?

]]>