-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Setup check for .well-known/caldav & carddav broken on Firefox #11773
Comments
I guess this might be an issue with Firefox not handling the redirect correctly? |
GitMate.io thinks possibly related issues are #8766 (Caldav ), #11733 (Fix a misleading setup check for .well-known/caldav & carddav), #7905 (CSS broken in firefox), and #5947 (webDAV PROPFIND). |
Looks like it's caused by my nginx proxy/apache setup: |
I handled this by adding location blocks to my nginx proxy configuration:
|
Thanks, I fixed it by adding Closing this now, as "not handling a badly setup reverse proxy" hardly seems to be a NC bug. |
Steps to reproduce
Expected behaviour
I should see (This happens in Chrome)
Actual behaviour
I see (Using Firefox)
Server configuration
Operating system: Linux: Devuan 2.0.0
Web server: Apache 2.4.25 (behind Nginx 1.14.0 proxy)
Database: PostgreSQL 6.9.6
PHP version: 7.0.30
Nextcloud version: 14.0.2 (Also happened in 14.0.2 RC2, but I figured it got fixed in #11738)
Updated from an older Nextcloud: Updated from previous RC
Client configuration
Browser: Firefox 60.2.2esr (64-bit)
Operating system: Linux: Devuan 2.0.0
What seems to happen:
Firefox:
https://fnp.tubul.net/.well-known/caldav
, which is redirected:Request headers
Response headers (empty body)
https://fnp.tubul.net/remote.php/dav/
returns a401
:Request headers
Response headers
Response body:
In Chrome (where the check works fine)
Request headers
Response headers (empty body)
https://fnp.tubul.net/remote.php/dav/
returns a207
:Request headers
Response headers
Response body:
The text was updated successfully, but these errors were encountered: