Hi Cliff,
just as a side note, the fact that you get those error in your inbox is
also a sign of a missconfiguration of your webserver. The Django error is
so to say a last resort, on a properly configured system those requests
would never reach Django at all.
Regards,
Florian
On Thursday,
Thanks for the quick response, Mark. That's awesome. Sorry I missed it in
the changelog.
Cheers,
Cliff
On Thursday, February 13, 2014 12:35:16 PM UTC-5, Mark Lavin wrote:
>
> This was already changed in https://code.djangoproject.com/ticket/19866which
> is part of 1.6. It's noted under the
This was already changed in https://code.djangoproject.com/ticket/19866
which is part of 1.6. It's noted under the minor
features https://docs.djangoproject.com/en/1.6/releases/1.6/#minor-features
SuspiciousOperation has been differentiated into a number of subclasses,
and each will log to a
Django devs,
I've noticed that the new ALLOWED_HOSTS causes the site
to return HTTP-500 errors whenever a user submits a request with an
HTTP_HOST header that is not allowed. This is flooding my developers'
inboxes with spurious error messages. The site is refusing the
requests as expected, but
