Unable to render templates

[rdegges]

Unable to render templates

[rdegges]

I'm not sure, this is the first time I've seen this. It looks as if you're accepting HTTPS requests DIRECTLY to your Django process, as opposed to having some sort of webserver / proxy intercept the SSL before passing the request to Django.

If that's what you're doing, you should really be using a web server of some sort in front of your Django app:

• gunicorn
• nginx
• something

[jsetting32]

Hi Randall,

Thank you for the quick response!

I read upon nginx and set it up but am not running it. I ran through a tutorial on uWSGI and nginx but wasn’t able to link the two together. This is the link I followed for the tutorial : http://uwsgi-docs.readthedocs.org/en/latest/tutorials/Django_and_nginx.html http://uwsgi-docs.readthedocs.org/en/latest/tutorials/Django_and_nginx.html

Is this going to put me on the right track? What would you recommend between the two (gunicorn vs nginx) ?

On Mar 27, 2015, at 11:26 AM, Randall Degges [email protected] wrote:

I'm not sure, this is the first time I've seen this. It looks as if you're accepting HTTPS requests DIRECTLY to your Django process, as opposed to having some sort of webserver / proxy intercept the SSL before passing the request to Django.

If that's what you're doing, you should really be using a web server of some sort in front of your Django app:

gunicorn
nginx
something
—
Reply to this email directly or view it on GitHub #26 (comment).

[rdegges]

I'm really only familiar with gunicorn, which is what I use. There are benefits / drawbacks to all of the different web servers, but in reality it doesn't matter so long as the webeserver itself is what's terminating the SSL connection.

I can't really speak to whether or not that tutorial is gonna help you though, sorry :(

You might be better off trying stackoverflow or something like that for this sort of help, as I'm sorta useless ><

[jsetting32]

Its no problem.

Thanks for your feedback, I greatly appreciate it!

On Mar 27, 2015, at 11:34 AM, Randall Degges [email protected] wrote:

I'm really only familiar with gunicorn, which is what I use. There are benefits / drawbacks to all of the different web servers, but in reality it doesn't matter so long as the webeserver itself is what's terminating the SSL connection.

I can't really speak to whether or not that tutorial is gonna help you though, sorry :(

You might be better off trying stackoverflow or something like that for this sort of help, as I'm sorta useless ><

—
Reply to this email directly or view it on GitHub #26 (comment).

[raul1991]

Hi randall,
Can you explain why django server should not be handling direct https connections ? Or some link

[rdegges]

It's not so much that the Django server shouldn't be terminating the SSL -- it's moreso a matter of speed and efficiency. EG: An actual webserver is going to be MUCH faster at handling the crypto operations, and this will also spare your Django process itself the pain of doing crypto on top of every connection.

AFAIK, this is the 'best practice' for scripting languages like Python where you're stuck on a single processor.