microsoft / microsoft/react-native-windows-samples
Fix unbroken checks for npmjs.com URLs hitting 403
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 544
- Forks
- 218
- PR merge metrics
- No merged PRs in 30d
Description
When queried npmjs.com URLs are queried from GitHub CI machines or from Microsoft's network (perhaps behind its proxies) fail with 403 Forbidden Request. Trying to add enough headers don't help too
$ curl -A "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36" \
-H "Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8" \
-H "Accept-Language: en-US,en;q=0.9" \
-H "Accept-Encoding: gzip, deflate, br" \
--compressed \
-L \
-I \
https://www.npmjs.com/
HTTP/2 403
These URLs are deemed broken by unbroken, thereby leading to documentation fixing PRs getting blocked due to these false positives.
Contributor guide
No contributing guide indexed for this repository
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 locating the unbroken configuration or CI entry point used to check npmjs.com URLs in this repository. Reproduce the 403 behavior from GitHub CI or Microsoft's network context, then determine how the check should handle these false positives. Done means documentation checks no longer block on affected npmjs.com URLs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100