Bug 52008 – OS X 10.14+ needs better redirects for .well-known DAVs

Bug 52008 - OS X 10.14+ needs better redirects for .well-known DAVs


Summary:	OS X 10.14+ needs better redirects for .well-known DAVs

Status:	REOPENED

Product:	UCS
Classification:	Unclassified
Component:	Apache
Version:	UCS 4.4
Hardware:	All Mac OS X 10.10

Importance:	P5 major (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:	UMC maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2020-09-14 12:37 CEST by andipilz
Modified:	2020-09-18 14:23 CEST (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?:	3: Will affect average number of installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.171
Enterprise Customer affected?:
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description andipilz 2020-09-14 12:37:48 CEST

When using NExtCloud (or OwnCloud) as DAV backend with UCS 4.4, OS X is not able to reliably use the function of ".well-known" due to improper redirects for:
- /.well-known/caldav
- /.well-known/carddav

This can be handled with a proper redirect on FQDN level adding in the file /etc/apache2/sites-enabled/default-ssl.conf

Below:

   ProxyPass /nextcloud http://127.0.0.1:40000/nextcloud retry=0
   ProxyPassReverse /nextcloud http://127.0.0.1:40000/nextcloud

The redirects to the FQDN:

Redirect 301 /.well-known/carddav https://<fqdn>/nextcloud/remote.php/dav
Redirect 301 /.well-known/caldav https://<fqdn>/nextcloud/remote.php/dav

Additionally it is necessary to have NextCloud and UCS-System on HTTPS as mandatory!!! (Might be enough to mention in handbook.)

Above could also apply to other collaboration backends like Kopano or OX? This I cannot confirm.

Comment 1 andipilz 2020-09-14 20:39:47 CEST

After some more investigation, I found also some hints in the documentation of NextCloud relating to services discovery: https://docs.nextcloud.com/server/18/admin_manual/issues/general_troubleshooting.html#service-discovery
in case, that - as with UCS - the NextCloud instance is address via /nextcloud.

Comment 2 Ingo Steuwer

2020-09-16 08:42:20 CEST

Please report issues and feature requests for Apps to the App Provider, contact addresses are given in the App description in the App catalogue.

Comment 3 andipilz 2020-09-18 14:23:56 CEST

Dear Ingo!
1. I checked this for next cloud and did not find it.
2. It is - as I write - also a problem across multiple apps, so it seems to be a problem in UCS. 
Though reopened, as I think, a few Mac users will be happy, what I see in the net and blog of Univention?
Best
Andreas