Django Lighttpd Deployment Addition

[dgt84]

It appears that lighttpd will IGNORE mod_rewrite rules within blocks using $HTTP["url"] to match on URLs (a fairly common thing to do to redirect to HTTPS for example). In order to do that you must NOT use $HTTP["url"], for example using "host" will work:

$HTTP["url"] =~ "/login" {
    url.redirect = "https://....../login"
} else $HTTP["host"] ~= ".*" {
    fastcgi.server = ....
}

I think the docs should be updated to reflect this as it will save others horrible headaches.

[Jacob]

[fixed formatting]

[Jacob]

We can't really expect to document every single quirk of every server Django could run on -- at a certain point, people are going to have to read the web server documentation, too. Still, this is probably worth mentioning somewhere.

[Gabriel Hurley]

if it should be mentioned anywhere it's in the ​lighttpd setup section of the deployment docs.

The thing that makes me uncertain that this should be brought up is that the example configuration currently does not give an example of the $HTTP["url"]-style syntax. It only shows the $HTTP["host"]-style configuration (which has always been my go-to configuration without even knowing about this issue).

So, the question is whether this issue--which is entirely incumbent on lighttpd--is so severe that it warrants mentioning even though we already encourage people in a direction that would avoid it?

[Gabriel Hurley]

I'll incorporate this into an overall lighttpd deployment review/overhaul.

[Aymeric Augustin]

Change UI/UX from NULL to False.

[Aymeric Augustin]

Change Easy pickings from NULL to False.

[Tim Graham]

FastCGI is being deprecated.