Details
-
Bug
-
Resolution: Fixed
-
Major
-
3.28.0
-
None
Description
At the moment nuget implementation works by v3 protocol if remote endwith ".json"
For example:
when remote = https://sitecore.myget.org/F/sc-packages/api/v3/index.json
then implementation works by V3 protocol
This rule doesn't work for all remotes and repositories. So, nexus should be ready to work with V3 remotes that don't endwith ".json"
How it can be implemented.
- Create a new one dropdown field called "Protocol" that will contain "V2 and V3"
- V3 should be selected by default
- With this solution, users will have a choice to select necessary nuget protocol
Reproduce steps.
- Create nuget proxy with remote that doesn't endwith ".json".
- Execute package install for example.
Actual:
nuget works by V2 protocol
Expected:
nuget works by selected protocol
Original issue
https://community.sonatype.com/t/override-nuget-proxy-repository-type/4920
Attachments
Issue Links
- implements
-
NEXUS-25506 change the Remote URL of the default nuget.org-proxy proxy repository to api version 3 compatible https://api.nuget.org/v3/index.json
-
- Closed
-
- is depended on by
-
NEXUS-25357 NuGet Proxy does not work with some third-party V3 repositories
-
- Closed
-