Skip to content
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

Closed
maartenba opened this issue Aug 19, 2015 · 2 comments
Closed

NuGet incorrectly treating authenticated V3 feed as V2 #1216

maartenba opened this issue Aug 19, 2015 · 2 comments
Assignees
Milestone

Comments

@maartenba
Copy link
Contributor

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.

@maartenba maartenba changed the title NuGet Visual Studio Extension incorrectly treating authenticated V3 feed as V2 NuGet incorrectly treating authenticated V3 feed as V2 Aug 20, 2015
@maartenba
Copy link
Contributor Author

Could be related to #1229 and #456

@yishaigalatzer yishaigalatzer added this to the 3.2 milestone Aug 21, 2015
@yishaigalatzer
Copy link

@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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants