WordPress / WordPress/Requests
[Task] Audit whether I18n domains are handled correctly everywhere
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 3.6k
- Forks
- 500
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 5
Description
Verify whether there are any code paths which could be reached where an international (multi-byte) domain would not have been translated to its ASCII value yet and non-multibyte-safe functions are being used.
This audit should, of course, safeguard this for the future with additional integration tests if/when needed.
Note: this audit should only verify this for the officially supported API. Not officially supported entry points can be disregarded.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the officially supported API entry points and checking where international domains are converted to ASCII before non-multibyte-safe functions are used. Review the existing integration tests and add coverage where needed; done means every supported path has been audited and the relevant behavior is protected by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100