New edition of the webapp protocol#367
Open
glpatcern wants to merge 2 commits into
Open
Conversation
5e2f23f to
a35cf17
Compare
mickenordin
reviewed
May 25, 2026
a35cf17 to
a72617e
Compare
mickenordin
reviewed
May 26, 2026
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
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.
Following discussions in the mailing list, this is the current proposal, for now only in terms of OpenAPI - the I-D is to come after we have consensus on this one.
A short summary:
-receiveprotocols, to signal the ability for an endpoint to receive a share (whereas so far what was advertised is the ability to send and serve shares). This was implicit withwebdav, but it's not for other optional protocols.webapp, thewebapp-receiveprotocol includes atargets, to signal all possible targets the endpoint can support.webdav-uricapability has been moved into auriattribute of thewebdav-receiveprotocol, following the new schema. This was never used so far, so such breaking change is not expected to actually break any implementation.webappshare now includestargets,permissions(replacingviewMode),appName, andappIcon.Questions:
-receiveprotocols, whilst preserving backwards compatibility for thewebdavprotocol?webappshare payload capture all that was discussed so far?