website Changelog /www/conservancy/middleware.py

Changelog - /www/conservancy/middleware.py @ 60010999d25f - showing 6 out of 6 revisions

bsturmfels	60010999d25f	8 months ago	Remove use of python3-future
bsturmfels	31e51a774223	2 years ago	Apply "object" changes only from `futurize --stage2`.
bsturmfels	05bee8b3c3b9	2 years ago	Apply `futurize --stage1` (safe) Python 2/3 compatibility changes.
Tom Marble	2bf594b86cb1	9 years ago	First pass at migration to Django 1.7
bkuhn	1e119efb7ac2	11 years ago	Incorporate conservancy_ssl middleware, etc. into main site, now that HTTPS fully supported. Incorporate conservancy_ssl middleware, etc. into main site, now that HTTPS fully supported. Previously, SSL on sfconservancy.org was supported using a self-signed cert only to handle the /admin/ portion of the site. Now that SSL is supported site-wide, and perfectly mirrors the content available via HTTP, the conservancy_ssl middleware, URLs, and settings are wholly deprecated and herein removed. The main site's urls.py now need adjusting to support /admin/, but additional code is needed in middleware.py to avoid accidentally serving /admin/ via HTTP instead of HTTPS. The latter code is untested; hopefully it works "out of the box". :)
bkuhn	bd6199f7b00e	14 years ago	Added middleware and management file