Opened 6 years ago

Closed 2 years ago

#10464 closed New feature (wontfix)

Django Lighttpd Deployment Addition

Reported by: dgt84 Owned by:
Component: Documentation Version: 1.0
Severity: Normal Keywords: deployment
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by jacob)

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.

Change History (10)

comment:1 Changed 6 years ago by jacob

  • Description modified (diff)
  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

[fixed formatting]

comment:2 Changed 6 years ago by jacob

  • Triage Stage changed from Unreviewed to Design decision needed

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.

comment:3 Changed 5 years ago by gabrielhurley

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?

comment:4 Changed 5 years ago by gabrielhurley

  • Keywords deployment added

comment:5 Changed 5 years ago by gabrielhurley

  • Owner changed from nobody to gabrielhurley
  • Status changed from new to assigned
  • Triage Stage changed from Design decision needed to Accepted

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

comment:6 Changed 5 years ago by gabrielhurley

  • Owner gabrielhurley deleted

comment:7 Changed 4 years ago by SmileyChris

  • Severity set to Normal
  • Type set to New feature

comment:8 Changed 3 years ago by aaugustin

  • UI/UX unset

Change UI/UX from NULL to False.

comment:9 Changed 3 years ago by aaugustin

  • Easy pickings unset

Change Easy pickings from NULL to False.

comment:10 Changed 2 years ago by timo

  • Resolution set to wontfix
  • Status changed from assigned to closed

FastCGI is being deprecated.

Note: See TracTickets for help on using tickets.
Back to Top