Improve documentation for development usage and expiration of clients #29
Conversation
This file contains hidden or 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
…f client metadata documents through the use of the Expires HTTP header
ThisIsMissEm
commented
Jan 10, 2025
Comment on lines
+201
to
+202
| For this purpose, it is recommended to use a service that generates and hosts client | ||
| metadata documents for development purposes. |
Contributor
Author
There was a problem hiding this comment.
I am really strongly encouraging this over the alternative of just sticking the document anywhere on the web with a public URL for development purposes.
Contributor
Author
|
@aaronpk did you have a chance to look at this? |
Contributor
Author
|
Some of this is superseded by #35 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is as was discussed in #23 (comment)
I did also add the restriction that the client metadata document response must be with a HTTP 200 OK status code, i.e., 3xx or 201 or other status codes should not be considered valid.
Also moved the development purposes section up from Security Considerations to the main part of the document.