Mention fetching https:// resources
#802
Open
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.
The "Reading Resources" sections of both
concepts/resources.mdx(in the User Guide) andserver/resources.mdx(in the Specification) only mention reading resources viaresources/read. However, the "Common URI Schemes" section ofserver/resources.mdxmentions that a client may fetch a resource directly from web if the resource URI has anhttps://scheme. Fetching the resource directly can have performance benefits, so it's worth calling more attention to this provision.This commit adds mention of the provision to both "Reading Resources" sections.