Description
Component
Forge
Have you ensured that all of these are up to date?
- Foundry
- Foundryup
What version of Foundry are you on?
forge 0.2.0 (8307d6d 2023-04-20T00:05:51.425008000Z)
What command(s) is the bug in?
forge verify-contract
Operating System
Linux
Describe the bug
I am running forge in an AWS EC2 instance and on verification keep getting a 403 error from Etherscan which results in the Failed to deserialize response: expected value at line 1 column 1 error as it returns html with a captcha rather than json.
I've reached out to Etherscan and this was their response:
We are aware of our CloudFlare protections being particularly sensitive to unknown automated scripts, and returning 403 responses as a result.
We're looking into whitelisting this at the moment, however a quick workaround for this would be to make your request more identifiable by attaching a User Agent string
My understanding is that reqwest doesn't set a default User-Agent header and so CloudFlare decides to block my request.
Does anyone know of a way to add a User-Agent header to outgoing requests on forge?
This seems like it currently affects just a small subset of users, although it would future proof everyone if a default user agent was set by forge/foundry. For example, curl automatically applies a default user agent so it would make sense for forge/foundry to do the same.