Repository navigation
TLS stack–based fingerprinting and blocking #2242
Replies: 7 comments
|
@borhanDZ don't think we can do much here but we've added an option to tlsi randomizer that you can try to use. |
|
@borhanDZ thanks! |
|
Hello all. I just now ran into this problem as well. In my particular case, I've found that the server is blocking the Edit: I couldn't find a way to drop the header using config or options, so I just made an mitmproxy script called remove_accept_charset.py, and that works. |
|
Hi @ehsandeep, Can you remove |
|
We compared several Akamai-fronted sites with and without |
|
Thanks @cdev95 and @Bundy01. We reproduced it locally with a server that rejects any request carrying @borhanDZ please retry once it lands. If you still get 403, it is the TLS fingerprinting @ehsandeep mentioned above. |


Thanks @cdev95 and @Bundy01. We reproduced it locally with a server that rejects any request carrying
Accept-Charset: curl got 200, httpx got 403, and-Hcould not remove the header. #2751 drops it; you can still add it back with-H "Accept-Charset: utf-8".@borhanDZ please retry once it lands. If you still get 403, it is the TLS fingerprinting @ehsandeep mentioned above.