Adnan, I'm really baffled by your response. No, my reasons for using SSL here is not because I'm afraid someone will sniff my data, We are talking here about `runserver`, which is the development server which is never used for production. The goal of `runserver` is to be able to easily test how your Django project behaves before you upload it to the real server. So the purpose of me wanting to use https on `runserver` are NOT because I think someone will hack into my local machine. It's because I want to test the behavior of the site. For example, I may have some complex redirection scheme, where some http pages on the site redirect you to https, and vice versa. So I would like to be able to test them out on the development machine before uploading to the server.
I checked out Stunnel. I'd prefer to avoid it. It's another program I will have to install and configure, and then I'll have to install and configure an SSL library, and then these things will have to be connected with `runserver`, which may result in problems and headache. The whole motivation to use `runserver` is how easy and painless it is, so I'd prefer it include these things out of the box. Ram. On Mon, Mar 1, 2010 at 2:53 AM, Adnan Sadzak <sad...@gmail.com> wrote: > If it's on your local machine there is no big sense to use ssl unles you > are paranoid. If someone can sniff local traffic, then ssl is useless. > Anyway, as Janusz said http://www.stunnel.org/ > > > On Mon, Mar 1, 2010 at 1:06 AM, Janusz Harkot <janusz.har...@gmail.com>wrote: > >> So you can use stunnel: http://www.stunnel.org/ >> >> J. >> >> -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
