-
Notifications
You must be signed in to change notification settings - Fork 225
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
Will AzCopy also be affected by *.azureedge.net
going away?
#2903
Comments
Hi @o-l-a-v Yes, we have migrated our aka ms links to the updated CDN URLs. The aka ms links will now point to URLs that start with |
@gapra-msft shall we expect |
PR already merged and live by @schoag-msft |
I have the same question as @droopy4096 , will |
For context to what @vijaytdh asks for. @schoag-msft said dotnet/core#9671 (comment):
AFAIK, unless you only want the latest version:
There is currently no domain in front of |
Thanks for the quick response. I probably didn't explain the use case very well:
|
Dotnet are changing all links pointing to any
azureedge.net
subdomain because it will likely be taken down shortly.I guess this affects AzCopy download links to?
Example redirect from
https://aka.ms/downloadazcopy-v10-windows
goes tohttps://azcopyvnext.azureedge.net/releases/release-10.27.1-20241113/azcopy_windows_amd64_10.27.1.zip
.The text was updated successfully, but these errors were encountered: