Skip to content
Discussion options

You must be logged in to vote

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 -H could 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.

Replies: 7 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by dogancanbakir
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
5 participants
Converted from issue

This discussion was converted from issue #2224 on August 17, 2025 02:11.