-
Notifications
You must be signed in to change notification settings - Fork 249
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.
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
NuGet incorrectly treating authenticated V3 feed as V2 #1216
Milestone
Comments
@feiling is going to look into it. If this is still not supported, I would suggest that myget drop this support until there is an actual NuGet3 support for this scenario. |
feiling
pushed a commit
to NuGetArchive/NuGet3
that referenced
this issue
Aug 25, 2015
feiling
pushed a commit
to NuGetArchive/NuGet3
that referenced
this issue
Aug 25, 2015
… as V2 The problem is that authentication was not supported for V3 feed. So when nuget checks if a feed is V3 or not, since accessing index.json fails because of authentication failure, nuget will treat the feed as V2. This change added authentication support.
This was referenced Aug 26, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When connecting to an authenticated V3 feed, the NuGet Visual Studio Extension prompts for credentials as expected. However on the next requests, the extension treats the feed as a V2 feed.
Steps to reproduce the issue:
When looking at the requests using Fiddler, the following flow can be seen:
Have not yet tested this with the 3.0 command line client.
The text was updated successfully, but these errors were encountered: