If you are using Apache to proxy to the Django admin interface (to enable the admin interface to be served under a different HTTPS host, for example), what do you suggest doing now that ADMIN_MEDIA_PREFIX has been removed?

e.g. ​https://secure.example.org/net-admin/ proxies internally to ​http://example.net/admin/ (and /admin/ is restricted to internal IPs only). STATIC_URL is set to /static/ so that it works fine for everything on the front end, but this then does not work as secure.example.org/static/ does not exist. If STATIC_URL is set to an absolute value of ​http://example.net/static/, then the admin will correctly give mixed HTTPS/HTTP warnings. There appear to be a lot of templates that would need overriding, so that doesn't seem like a good way to go. We use this set up on a number of sites, so it would be good if there was a simple way it could be continued.

If you are using Apache to proxy to the Django admin interface (to enable the admin interface to be served under a different HTTPS host, for example), what do you suggest doing now that ADMIN_MEDIA_PREFIX has been removed?

e.g. ​https://secure.example.org/net-admin/ proxies internally to ​http://example.net/admin/ (and /admin/ is restricted to internal IPs only). STATIC_URL is set to /static/ so that it works fine for everything on the front end, but this then does not work as secure.example.org/static/ does not exist. If STATIC_URL is set to an absolute value of ​http://example.net/static/, then the admin will correctly give mixed HTTPS/HTTP warnings. There appear to be a lot of templates that would need overriding, so that doesn't seem like a good way to go. We use this set up on a number of sites, so it would be good if there was a simple way it could be continued.