My settings look like this
ALLOWED_HOSTS = [
* '.mydomain.com', # Allow domain and subdomains '.mydomain.com.', #
Also allow FQDN and subdomains u'mp-ip-add-ress',*
]
I am getting the errors for my server's IP address
Invalid HTTP_HOST header: 'x.x.x.x'. You may need to add u'x.x.x.x' to
ALLOWED_HOSTS.
BUT also for so many suspicious names like this
- Invalid HTTP_HOST header: '4331780'.You may need to add u'4331780' to
ALLOWED_HOSTS.
- Invalid HTTP_HOST header: 'testp1.piwo.pila.pl'.You may need to add
u'testp1.piwo.pila.pl' to ALLOWED_HOSTS.
- Invalid HTTP_HOST header: 'www.cloud.ph'.You may need to add
u'www.cloud.ph' to ALLOWED_HOSTS
All of them say the following
*No stack trace availableRequest repr() unavailable. *
In the morning I have around 20-30 such emails..
On Monday, May 26, 2014 at 5:04:23 PM UTC+5:30, Federico Bruni wrote:
>
> I've been getting this error message since I've deployed my mezzanine
> website:
> [Django] ERROR: Invalid HTTP_HOST header: 'domain.com'.You may need to
> add u'domain.com' to ALLOWED_HOSTS
>
> where domain.com is most of the times the IP of the server, few times a
> secondary domain which redirects to the main one and one time www.fbi.gov
> :-)
>
> I've read the pages below, so I think that I can just ignore the error
> (I'm sure that my ALLOWED_HOSTS is restrictive).
> I guess that I can wait for Django >= 1.7b4 in Mezzanine and then I won't
> get any error message. Right?
>
>
> http://stackoverflow.com/questions/15238506/djangos-suspiciousoperation-invalid-http-host-header
> https://code.djangoproject.com/ticket/19866
>
> https://github.com/django/django/commit/d228c1192ed59ab0114d9eba82ac99df611652d2
>
> (added in django 1.7b4)
>
>
--
You received this message because you are subscribed to the Google Groups
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
