Skip the CDN for nuget.org/nuget.exe

[jeffhandley]

We need to skip the CDN when serving nuget.org/nuget.exe, serving it directly from blob storage. This will allow the new version to be available immediately after pushing NuGet.CommandLine.

[TimLovellSmith]

We could either do that, or we could make the site redirect you to a versioned URL on the CDN.
We appear to have a bunch of blobs like Nuget.2.7.exe sitting around - I haven't looked at how they got there yet, but this seems like a way to get around the caching issue with advantaages - redirecting to the latest one of these can not only avoids the CDN caching but also avoid caching on the client and intermediate proxies.

[bhuvak]

Marking it as P1 for next iteration. We need to get it fixed before 2.7.1 release.
The CDN team also suggested having versioned URL similar to Tim's suggestion.

[TimLovellSmith]

Is this issue in the right milestone?

[analogrelay]

Sounds like no. Throw it in next milestone?

[TimLovellSmith]

Done, moved to 10/18

[bhuvak]

To skip for the specific container ("Donwloads"), can we set it as "Private" ? It sounds like a simple and straightforward solution for me. Would like to hear other's thoughts ...

[analogrelay]

No, Private means it can only be accessed with the Account Key. The gallery just redirects to the blob/CDN (or at least it should) so making it Private would mean it can't be downloaded :). We just need to be able to provide a "skipCDN" flag in to the File Storage Service when we request a file download URL.

[OlRedHawk]

yep

[xavierdecoster]

@deepakaravindr is this one still relevant?

[TimLovellSmith]

The was issue that there's no good way to tell CDN to refresh a certain URL and start serving latest content there, I expect that hasn't changed.
Have you considered doing anything to work around this from the client side like append a dummy query ?_=uniquifier to force bypassing CDN cache when getting nuget.exe?

[robertmuehsig]

Just scrolled through old issues: Is this still relevant with dist.nuget.org in place?

I also noticed that https://nuget.org/nuget.exe will serve version 2.8.6 - is this by design?

[skofman1]

https://nuget.org/nuget.exe is no longer used. Closing the issue.