fix(OCM): Fix OCM provider discovery for servers without beautiful URLs

[nickvergessen]

• Followup to OCM Services #39574

Resolves

• This allows to do federation with instances again that do not support "beautiful" URLs at all.

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)

[nickvergessen]

/backport to stable27

[nickvergessen]

/backport to stable26

[kesselb]

I'm not familiar with ocm 🙈

1. Isn't that against the spec to query index.php/ocm-provider
2. Wouldn't that break if the remote instance is not Nextcloud

[nickvergessen]

Isn't that against the spec to query index.php/ocm-provider

If it is, we need to recreate the folder with it's index.php like it was before #39574

Wouldn't that break if the remote instance is not Nextcloud

Right. Quick fix suggestion: go back to "first query without index.php and if that gives a 404 we try with index.php, or implement the folder again.

[level420]

@nickvergessen could this also solve the problem that since v 27.1.x (now having 27.1.3) I'm getting warnings about unresolvable "/ocm-provider/" in the security and warnings section?

My instances are running without pretty urls enabled, and https://myinstance.com/index.php/ocm-provider/ works, but https://myinstance.com/ocm-provider/ not.

I'm running a docker stack using the current nextcloud docker image nextcloud:27.1-fpm which is behind an apache httpd proxy.

[nickvergessen]

yeah that was exactly the attempt.

atm you can fix it by running occ maintenance:update:htaccess (Docs at https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/occ_command.html )

[nickvergessen]

@sorbaugh @ArtificialOwl What's the state with this.
With the upcoming Talk federation work it will be quite more annoying again.