Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CreateOCMShareRequest.Protocol vs CreateOCMShareRequest.Opaque.Map["protocol"] #2402

Closed
michielbdejong opened this issue Dec 27, 2021 · 2 comments

Comments

@michielbdejong
Copy link
Contributor

Looking at this definition it seems that CreateOCMShare requests have a Protocol field.

But looking at this server code and this client code it seems that the protocol is put into the root opaque instead?

Is this intentional?

CC @redblom

@michielbdejong michielbdejong changed the title CreateOCMShareRequest.Protocol vs CreateOCMShareRequest.Opaque.Map["protocol"] vs CreateOCMShareRequest.Protocol vs CreateOCMShareRequest.Opaque.Map["protocol"] Dec 27, 2021
@michielbdejong
Copy link
Contributor Author

michielbdejong commented Dec 27, 2021

If not I can easily switch it around, let me know.

I'm adding the req.protocol.options.sharedSecret from https://cs3org.github.io/OCM-API/docs.html#/paths/~1shares/post which is needed for the webdav protocol and wanted to put it into CreateOCMShareRequest.Protocol but then I noticed your use of CreateOCMShareRequest.Opaque.Map["protocol"] and thought I should probably check first. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant