The technical issue is that a URL like this:
http://domain.tld/script/path
is split into these two variables by Lighttpd:
SCRIPT_NAME: /script
PATH_INFO: /path
and Django wants this:
SCRIPT_NAME:
PATH_INFO: /script/path
Your example is a bit misleading/lacking. Both
Antonis,
Well truth be told I'm with uwsgi only because of the snowball effect
you're alluding to, namely we have so many options I'm like looking
on-line for what the most popular and recommended one is, and uwsgi has
a huge fan base. As to server, I opted for lighttpd only because I
That particular issue may be a lighttpd issue, but my question is more general.
Unfortunately I don't remember the kind of trouble I was having with uwsgi.
Are there any people who have used both uwsgi and gunicorn and have a preference
for the former? What benefits have they seen?
Antonis
You're missing the fact that it's the scgi module of lighttpd is what
is causing it. uwsgi shouldn't fix it, as it has no idea if this is
intentional, for example when using mounts [1].
As can be seen in the WSGI spec, the WSGI client (uwsgi / gunicorn /
whathaveyou) should trust what is provided
> Alas it's a tad complicated and I'll try and publish a module with the fix
> some time soon (it relates to lighttpd, uwsgi, django interactions and the
> management of SCRIPT_NAME and PATH_INFO environment variables which lighttpd
> doesn't do to Django's satisfaction and so it needs tweaking
Well, not a lot of insight from the broader community on this one, but a
warm thank you to Melvyn Sopacua who took the time to think about it a
bit and apply his experience which led me to:
/usr/local/lib/python3.5/dist-packages/django/urls/base.py
where I could instrument Django a bit
Humor me and call it list_view in the pattern and template references.
--
Melvyn Sopacua
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
7 matches
Mail list logo
