Comments on: Simplest WordPress Permalink Solution for Lighttpd

By: tw

tw — Sat, 31 Jul 2010 13:48:03 +0000

works perfectly. Thank you.

I do like the quick and dirty way of getting things done as long as it just works.

By: Chrische

Chrische — Sat, 24 Apr 2010 15:32:09 +0000

Quick and dirty.
Clean solution including multi-wordpress support isn’t so much more work: http://www.chrische.de/2010/04/lighttpd-in-verbindung-mit-wordpress-und-rewrites/

By: puma

puma — Thu, 12 Mar 2009 03:17:08 +0000

really usefuyl to me,thanx alot!

By: Wing Loon

Wing Loon — Tue, 03 Mar 2009 10:33:44 +0000

…thank you for this great solution and it works for me,

By: Andrew

Andrew — Tue, 24 Feb 2009 21:22:11 +0000

“If you were able to see this page, and comment on it, I’m assuming you got more than a 404 error.”

That doesn’t mean that your server isn’t sending back a 404 status code in the header. I did check, and I am getting back 200 OK, but I would be worried that future LightHTTP versions send back 404 headers with your settings and it would absolutely kill your SEO.

By: Daniel Hahler

Daniel Hahler — Mon, 23 Feb 2009 23:48:14 +0000

Yes, that’s a clever approach and I’ve been using it for a while with b2evolution, too.

But, you’ll lose the PATH_INFO information, e.g. from http://example.com/index.php/PATH_INFO

You may grep WP’s source for PATH_INFO, to see if it gets used anywhere.

I’m currently using a magnet/LUA script.

By: Dean

Dean — Mon, 23 Feb 2009 21:42:09 +0000

Just check…it’s returning 200 OK.

You have got something 404ing from google though Christer.

By: Christer Edwards

Christer Edwards — Mon, 23 Feb 2009 18:34:38 +0000

@Joseph – that’s the thing though. It isn’t displaying a 404 error for every single page on the blog. If you were able to see this page, and comment on it, I’m assuming you got more than a 404 error.

By: Joseph Scott

Joseph Scott — Mon, 23 Feb 2009 17:42:45 +0000

It does “work” in the sense that it gets the URL redirects to work. But as Andrew mentioned, probably not a good idea to return HTTP status 404 (indicating that the content could not be found) for every single page on your blog.

By: Christer Edwards

Christer Edwards — Mon, 23 Feb 2009 17:28:47 +0000

@Andrew – At first glance it doesn’t make much sense how/why it works, but it does. This is the only line of code re: URL rewriting I have on this blog but as you can tell all the URL seem to be working just fine.