Elicitation: clarify clickable URL language #1811
Merged
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
nbarbettini
commented
Nov 13, 2025
Comment on lines
-704
to
-705
| 1. **MUST NOT** include plain text sensitive information about the end-user, including credentials, personal identifiable information, etc., in the URL sent to the client. | ||
| 1. **MUST NOT** provide a URL which is pre-authenticated to access a protected resource, as the URL could be used to impersonate the user by a malicious client. |
Contributor
Author
There was a problem hiding this comment.
These two MUSTs did not change substantively
Comment on lines
-702
to
-703
| 1. **MUST NOT** include URLs in any message or schema fields as part of a form mode elicitation request. | ||
| 1. **MUST NOT** include URLs in any message or schema fields as part of an URL mode elicitation request, except for the `url` field. |
Contributor
Author
There was a problem hiding this comment.
Removed these two MUSTs in favor of a SHOULD
| 1. **SHOULD** use HTTPS URLs for non-development environments. | ||
| 1. **MUST NOT** include sensitive information about the end-user, including credentials, personal identifiable information, etc., in the URL sent to the client in a URL elicitation request. | ||
| 2. **MUST NOT** provide a URL which is pre-authenticated to access a protected resource, as the URL could be used to impersonate the user by a malicious client. | ||
| 3. **SHOULD NOT** include URLs intended to be clickable in any field of a form mode elicitation request. |
Contributor
Author
There was a problem hiding this comment.
Added this SHOULD - still worth calling out IMO, but I think for conformance purposes it can be a SHOULD and doesn't need to be a failing case.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Motivation and Context
Fast-follow to #887 to address a spec language clarification discussed with @pcarleton.
How Has This Been Tested?
N/A
Breaking Changes
N/A
Types of changes
Checklist