Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support IDNA2003 #3229

Open
jruere opened this issue Jun 25, 2024 · 2 comments · May be fixed by #3284
Open

Support IDNA2003 #3229

jruere opened this issue Jun 25, 2024 · 2 comments · May be fixed by #3284

Comments

@jruere
Copy link

jruere commented Jun 25, 2024

From: #2586

Accept already encoded domains, and do not attempt to decode them. This way, any IDNA encoding would be accepted, and it's up to the application to decide the policy of what to actually accept.
@jruere
Copy link
Author

jruere commented Jun 25, 2024

I don't think the proposed change would help with redirections to IDNA2003 sites.

@tomchristie
Copy link
Member

Accept already encoded domains, and do not attempt to decode them.

Yes, this would be the smart policy.

@waketzheng waketzheng linked a pull request Aug 27, 2024 that will close this issue
Open
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: suppport IDNA2003 waketzheng/httpx
2 participants
@tomchristie @jruere