Work around recent Akamai/Microsoft issues #16349
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At the moment, Microsoft Office and related casks fail audit due to failure to fetch a product homepage from the main Microsoft site (https://www.microsoft.com/) served by Akamai CDN. The failure is severe and weird: no status code is received as the connection is reset.
The analysis revealed the issue is linked to
User-Agent
andAccept-Language
headers parsing. Homebrew uses involved user agent strings and has language hardcoded asen
.The simplest workaround is to use a simple user agent string when checking homepage availability if the cask is in an audit exceptions list.
Merging this would fix Microsoft Office updates (including Homebrew/homebrew-cask#162671)
brew style
with your changes locally?brew typecheck
with your changes locally?brew tests
with your changes locally?