> So either Django is not a compliant WSGI app or uWSGI is unable to mount
> a standard WSGI application to the root location in nginx without using
> magic rewrites?
>
> Eienne
>
Neither of the two, you were asking about mounting in a sub-uri in the
previous posts, that requires some kind of rul
So either Django is not a compliant WSGI app or uWSGI is unable to mount
a standard WSGI application to the root location in nginx without using
magic rewrites?
Eienne
Le 2017-08-06 à 06:28, Roberto De Ioris a écrit :
This is what any compliant WSGI server (included uWSGI) expects:
https:/
> On Sat, Aug 05, 2017 at 11:47:24AM -0400, Etienne Robillard wrote:
>
> Hi there,
>
>> The workaround suggested below is not working.
>
> From the words here, it is not clear to me what specific configuration
> you are using.
>
>> The only case where
>> Django correctly handle uWSGI transport is
On Sat, Aug 05, 2017 at 11:47:24AM -0400, Etienne Robillard wrote:
Hi there,
> The workaround suggested below is not working.
>From the words here, it is not clear to me what specific configuration
you are using.
> The only case where
> Django correctly handle uWSGI transport is when PATH_INFO
On Sat, Aug 05, 2017 at 03:24:28PM -0400, Etienne Robillard wrote:
Hi there,
> The $http_pragma is not properly defined in
> http://nginx.org/en/docs/varindex.html
It's the one after "$http2" and before "$https".
> Is that a custom variable or is defined in nginx?
$http_anything is defined in
Hello everyone
I want to use variables in proxy_cache_valid directive like the syntax
below
« set $var10 "10m";
proxy_cache_valid 200 $var10; »
but I get the error « invalid time value »
so I tried to tweak a little in the ngx_http_file_cache.c file and I added
the following lines:
«ngx
