You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having exactly the same problem. I can't allow traffic that looks like this through the firewall.
Heck, even disregarding the user agent string and allowing the traffic based on the agent's IP address for initial HSTS preload checks, the IP address might change in future.
Ideally, a change of user agent string is also complemented by introducing a set of verifiable DNS names visible in reverse and forward IP address lookups of the agent (similar to how Google Bot can be reliably recognised).
Currently, it seems to be
Go-http-client/2.0
which doesn't tell the purpose for the request.For example SSL Labs test sends
SSL Labs https://www.ssllabs.com/about/assessment.html)
as user-agent.The text was updated successfully, but these errors were encountered: