Remove option to use HTTP HEAD from API-design-guidelines.md #50
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
HEAD requests are not suitable for network APIs managing dynamic data
eric-murray
requested review from
shilpa-padgaonkar,
rartych and
patrice-conil
as code owners
rartych
approved these changes
Aug 29, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
HEAD requests are not suitable for network APIs managing dynamic data and there use should be prohibited. There are alternatives to HEAD requests if the purpose is to see whether the data has changed since last requested - for example, the
If-Modified-Sinceheader.Which issue(s) this PR fixes:
Fixes #28
Special notes for reviewers:
No APIs currently define HEAD requests
Changelog input
Additional documentation
N/A