From 4699b201a95388033ab5c02c3c8bbff7b5f5096b Mon Sep 17 00:00:00 2001
From: Sunil Mohan Adapa <sunilad@thoughtworks.com>
Date: Wed, 15 Feb 2017 16:28:46 +0530
Subject: [PATCH] Remove use of stronghold whitelisting

This is no longer necessary as both the URLs have been explicitly
marked as public views.
---
 plinth/__main__.py | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/plinth/__main__.py b/plinth/__main__.py
index 67945be38..de5aba07e 100644
--- a/plinth/__main__.py
+++ b/plinth/__main__.py
@@ -205,13 +205,6 @@ def configure_django():
     if cfg.secure_proxy_ssl_header:
         secure_proxy_ssl_header = (cfg.secure_proxy_ssl_header, 'https')
 
-    # XXX: We want use STRONGHOLD_PUBLIC_NAMED_URLS, however, due to a
-    # bug in stronghold, it compares request.path_info with reversed
-    # URLs.  This leads to a mismatch when script_prefix is set.
-    # Remove this hack once the bug is fixed.  See:
-    # https://github.com/mgrouchy/django-stronghold/issues/52
-    public_urls = ('/accounts/login/', '/accounts/logout/')
-
     django.conf.settings.configure(
         ALLOWED_HOSTS=['*'],
         CACHES={'default':
@@ -244,7 +237,6 @@ def configure_django():
         SESSION_ENGINE='django.contrib.sessions.backends.file',
         SESSION_FILE_PATH=sessions_directory,
         STATIC_URL='/'.join([cfg.server_dir, 'static/']).replace('//', '/'),
-        STRONGHOLD_PUBLIC_URLS=public_urls,
         TEMPLATES=templates,
         USE_L10N=True,
         USE_X_FORWARDED_HOST=cfg.use_x_forwarded_host)