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
{{ message }}
Repository navigation
[webconnectivity]: Support user-agent strings in request headers to bypass scrapper security #1741
although the websites are accessible through the browser. On further inspection, we found that this is also the case with other http clients like curl and we require a minimum number of user-agent request headers in order to access the website:
@hellais pointed out that some work on the scrapper invasion strategies in the past reflected that WAFs will also match the TLS stack to the user-agent strings and consider the ordering of HTTP headers in determining what to do. The go stdlib does not support maintaining the order of request headers but we should in my opinion still support user-agent strings in the experiment as a start. These are the headers that should be used for Chrome 132:
Activity
DecFox commentedon Sep 18, 2025
@hellais pointed out that some work on the scrapper invasion strategies in the past reflected that WAFs will also match the TLS stack to the user-agent strings and consider the ordering of HTTP headers in determining what to do. The go stdlib does not support maintaining the order of request headers but we should in my opinion still support user-agent strings in the experiment as a start. These are the headers that should be used for Chrome 132:
[-][webconnectivity]: Support user-agent strings in request headers to bypass by scrapper security[/-]