Incompatible URLs used when downloading from NuGet.org
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Hey there.
I'm a PM on the NuGet.org team and I wanted to reach out
NuGet.org is migrating towards a new multi-CDN infrastructure: NuGet/Announcements#60
Going forward, not all of our CDN providers will support case insensitive URLs. As a result, nuget.org's V3 API to download packages’ content will only support lowercased package ID and version values, as documented here: https://docs.microsoft.com/en-us/nuget/api/package-base-address-resource
For example:
Recently we received requests with uppercased package ID or versions from a client with user agent “Paket”. We recommend you update your project to use lowercased package ID and versions when downloading packages’ content using nuget.org’s V3 API.
Feel free to reach out to us at support@nuget.org or on GitHub at https://github.com/NuGet/NuGetGallery/issues if you have any questions or concerns.
Best regards,
NuGet Team
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
Read the NuGet V3 package base-address documentation and trace how Paket constructs package download URLs. Done means downloads use lowercased package IDs and versions, matching the URL format required by NuGet.org.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100