-
Notifications
You must be signed in to change notification settings - Fork 183
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
Update cache-control for newly created blobs #1066
Conversation
@@ -229,7 +229,7 @@ function Upload-Blobs | |||
if ($UploadLatest -and ($latestVersion -eq $DocVersion)) | |||
{ | |||
Write-Host "Uploading $($PkgName) to latest folder in $($DocDest)..." | |||
& $($AzCopy) cp "$($DocDir)/**" "$($DocDest)/$($PkgName)/latest$($SASKey)" --recursive=true | |||
& $($AzCopy) cp "$($DocDir)/**" "$($DocDest)/$($PkgName)/latest$($SASKey)" --recursive=true --cache-control "max-age=300, must-revalidate" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't we also want to add this to our versions file updated? Based on the issue I thought that was the file they were interested in making sure the cache expires.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have already updated the existing ones for temporary fix. I was thinking we might only need to fix newly created one. But after a second though, it still has the chance of overwriting the existing version doc. So I will update the rest places(new and existing ones).
The following pipelines have been queued for testing: |
Updated the existing ones using azure powershell.
Update the script here to make sure we update the cache-control for newly created blobs.
Fixed issue: #976