Nextcloud AIO Caddy reverse proxy status code differ to OCS API manual status codes

Nextcloud version (eg, 20.0.5): 25.04
Operating system and version (eg, Ubuntu 20.04): Ubuntu Server 22.04
Nextcloud AIO Docker Setup: 4.5.0
Caddy Reverse Proxy: 2.6.4

The issue you are facing:
I use the recommended easy to set up Nextcloud AIO containers with the caddy reverse proxy setup. The setup is running and everything is fine.

However, if using the OCS API, I get different status codes as expected. For example, for the get all shares request, I get a status code of 200 as a success result instead of a 100.

This already led to problems, in this case here for the Les Pas app, where return codes of 409 instead of 404 let to undesired behavior.

  1. So my question is, if that is normal for this Nextcloud AIO caddy setup?
  2. If so, should that be documented?

Steps to replicate it:

  1. Use the Nextcloud AIO setup with caddy
  2. curl -u $USER:$PW -X GET "https://${BASE_URL}/ocs/v2.php/apps/files_sharing/api/v1/shares" -H "OCS-APIRequest: true"
  3. Check the status code, if it is 100 or 200

Thank you :slight_smile: