Possible statuscodes from the OCS share API

Open Beginner friendly
#10,899 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Domain
api, documentation

Research direction

Open the OCS share API documentation at the URL in the issue and locate the “Create a new Share” status-code list. Compare the documented success response with the XML shown for Nextcloud 27.0.1, then update the entry so the documentation matches the API; done means the listed response codes are accurate.

Written by the indexing model from the issue text.

Description

1. to develop bug feature: sharing good first issue manual: developer

The API lists at URL https://docs.nextcloud.com/server/latest/developer_manual/client_apis/OCS/ocs-share-api.html under "Create a new Share" possible status codes:

100 - successful
400 - unknown share type
403 - public upload was disabled by the admin
404 - file couldn’t be shared

However, when I create a new share on the current stable version 27.0.1 an d create a new share, I get the following XML back after a successful creation, indicating that the statuscode for a successful share creation is 200, not 100.

<?xml version="1.0"?> <ocs> <meta> <status>ok</status> <statuscode>200</statuscode> <message>OK</message> </meta> <data> [...]

Dominant language
JavaScript
Stars
628
Forks
2.5k
Avg merge
1d 23h
Merged PRs (30d)
133

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nextcloud/documentation

All issues in nextcloud/documentation

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.