oh ok got you.
Thanks
On Thu, Oct 13, 2016 11:47 AM, Ryne Everett ryneever...@gmail.com
wrote:
If you want your configuration to more closely resemble the default nginx
template you can uncomment those ssl lines and use the django ssl middleware
instead.
On Thu, Oct 13, 2016 at 11:33 AM,
If you want your configuration to more closely resemble the default nginx
template you can uncomment those ssl lines and use the django ssl
middleware instead.
On Thu, Oct 13, 2016 at 11:33 AM, Akhlaq Rao wrote:
> ok so nginx template for SSL entries no good anymore, were
ok so nginx template for SSL entries no good anymore, were they directly
connected to SSLRedirectMiddleWare?
Thanks,A
On Thu, Oct 13, 2016 11:23 AM, Ryne Everett ryneever...@gmail.com
wrote:
SSLRedirectMiddleware would not solve that problem, all it does is redirect to
https.
The way I
SSLRedirectMiddleware would not solve that problem, all it does is redirect
to https.
The way I handle this is having a line like ` return 301
https://$host$request_uri;
` in my server block listening on port 80, and another server block
listening on port 443 that actually proxies to django.
On
Hi Ryne,
I totally get it, but if I do not useSSLRedirectMiddleware then I don't see SSL
Enable form in the Admin Settings. Do you know how do I enable SSL without
usingSSLRedirectMiddleware? if I go to my frontend nginx all the SSL related
entries are commented out.
server {
listen 80; #
Whoops. I just pushed a fix for that bug.
However, you still shouldn't be using that middleware. If you're going to
use an SSL middleware, use django's (
https://docs.djangoproject.com/en/1.10/ref/middleware/#module-django.middleware.security).
However, my recommendation is to handle the redirect
If it's deprecated then how do we enable SSL now? when I enable it I get
the following error:
unhandled exception in thread started by .wrapper at 0x10ff97950>
Traceback (most recent call last):
File