Around the end of June I switched my server to lighttpd but, due to some unknown issue, all my wordpress pages using rewrites were giving back 404’s - even though the page was being displayed correctly. This basically broke my feeds as most feed readers discard 404’s even if the server passes content back too.
I’ve decided to take the plunge again since both Wordpress and lighttpd have come along a revision or two. I simply want to reduce the amount of memory being used on my Linode and, with a bit of luck and assuming the 404 issue has dissapeared, I’ll have oodles of RAM to spare for other bits and pieces like TurboGears.
Cliff Wells | 12-Jan-06 at 3:13 pm | Permalink
Perhaps setting the 404 handler in lighttpd.conf to point to index.php (or whatever it is that wordpress uses)?
Splee | 12-Jan-06 at 3:40 pm | Permalink
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. :)