Invalid HTTP_HOST header about deploy HOT 10 CLOSED

Invalid HTTP_HOST header: '46.43.2.235'. You may need to add '46.43.2.235' to ALLOWED_HOSTS.
Invalid HTTP_HOST header: '46.43.2.235:443'. You may need to add '46.43.2.235' to ALLOWED_HOSTS.

Is there a use case for this one? Currently I think the only reason we would see this is bots trying to crawl us. (In fact, on a lot of our servers we set up an default apache placeholder site for bots to see).

Invalid HTTP_HOST header: 'live.standard-search.opencontracting.uk0.bigv.io'. You may need to add 'live.standard-search.opencontracting.uk0.bigv.io' to ALLOWED_HOSTS.

www.live.standard-search.opencontracting.uk0.bigv.io is however already set up as an ALLOWED_HOSTS and an SSL cert name - for the same avoiding-bots reason as above, can we leave it as this?

from deploy.

Aha. Is there a way to quiet specific HTTP_HOST errors, so that we don't continually get new reports in Sentry?

from deploy.

I see the problem - we do have an default host in place for HTTP crawlers, but not for HTTPS crawlers - ie h t t p://46.43.2.235/ gets placeholder, h t t p s://46.43.2.235/ gets site and generates a sentry error.

We can look into that.

from deploy.

Look into stopping HTTPS crawlers hitting real sites and generating errors

from deploy.

This has been solved in a few different ways:

• Re-configure the DisallowedHost logger to be muted
• Ignore the DisallowedHost logger via Sentry's configuration
• Ignore the Sentry issues

For now I ignored them until 2038-01-19 03:14 in Sentry.

from deploy.

Also occurs on Data Review Tool (and presumably any Django app with Sentry installed).

from deploy.

Commented in our deploy repository in OpenDataServices/opendataservices-deploy#88

from deploy.

I'm reconfiguring loggers.

• toucan
• cove-ocds
• cove-oc4ids
• standard-search OpenDataServices/standard-search#25

from deploy.

Done and deployed. There's an open PR for standard-search. Once closed, we can resolve the open issues in Sentry.

from deploy.

PR for standard-search is merged now.

Looks to me like all the open issues in Sentry are gone already.

from deploy.