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

ocm-provider end-point doesn't work #14247

Closed
schiessle opened this issue Feb 16, 2019 · 3 comments · Fixed by #14255
Closed

ocm-provider end-point doesn't work #14247

schiessle opened this issue Feb 16, 2019 · 3 comments · Fixed by #14255

Comments

@schiessle
Copy link
Member

Tested with Nextcloud 15.0.4

curl -X GET http://localhost:70/server/ocm-provider/

should return a JSON object which describes the OCM capabilities. This works on my dev environment but not on productive instances like c.nc.com. I assume that it doesn't work because of the rewrite rules in the .htaccess file. But /ocs-provider/ works and there is no special rule for this end-point in the .htaccess and I can't spot a obvious reason why it doesn't work for /ocm-provider/

@rullzer @MorrisJobke any idea?

@rullzer
Copy link
Member

rullzer commented Feb 16, 2019

Yeah. Seems there need to be an explit rule in https://github.com/nextcloud/server/blob/master/.htaccess#L56-L70

Since with pretty urls we pipe everything trough index.php. Where this does 💥

@rullzer
Copy link
Member

rullzer commented Feb 16, 2019

And yeah there is a special rule

$content .= "\n RewriteCond %{REQUEST_FILENAME} !/ocs-provider/";

@schiessle
Copy link
Member Author

Ah, I only looked at the .htaccess in the git-repository which doesn't has a special rule. I created a pull request, do you think it is enough to add it to the setup.php or should we also add it to the existing .htaccess?

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

Successfully merging a pull request may close this issue.

3 participants