After ver. 4.10.0, Nextcloud URLs do not take subpath into account

[EthanLatimerGB]

Describe the bug
When attempting to connect with a server URL of https://domain.name.com/nextcloud, where a reverse proxy is used when attempting to connect with the /nextcloud subpath, I get a 405 error returned. (ref. Image 1)

Previous versions of the flatpak worked correctly, in terms of the subpath being accepted (ref. Image 2). But on investigation in my NGINX logs, planify does not have the /nextcoud/subpath included. Instead, it tried to resolve as if the URL was https://domain.name.com/. (ref. Image 3)

Was investigating and the flatpak has this bug after hash=27495ac202bb187fb0923984bb2439f3a25211a87225b17cecfcd6f237729b3b. Which is ver. 4.10.0.

To Reproduce
Steps to reproduce the behavior:

1. Go to preferences
2. Select integrations
3. Select + to add a new account
4. Select nextcloud
5. Enter a URL for a service that has a /nextcloud subpage (reverse proxy)
6. Enter login details and select login.

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
Image 1

Image 2 - Planify before 4.10.0 would use the correct URL

Image 3 - Planify currently resolves to this URL

Desktop (please complete the following information):

• OS or DE: Fedora 40 Workstation (GNOME)
• Version: 4.10.6

Additional context
n/a

[alainm23]

Hi and thank you for reporting this issue, I would like to ask you to tell me which url your browser redirects to when you enter this link.

https://domain.name.com/nextcloud/.well-known/caldav
https://domain.name.com/.well-known/caldav

Screencast.from.2024-08-07.06-06-50.mp4

[EthanLatimerGB]

Hi Alain, on entering those two links:

Upon entering /nextcloud/.well-known/caldav I get redirected.
Screencast from 2024-08-07 13-33-53.webm

[EthanLatimerGB]

Just in case I misconfigured my reverse proxy, here is the configuration for the /nextcloud/ redirect in NGINX:

server {
	server_name ethanlatimer.ddns.net;
	client_max_body_size 10G;
	client_body_buffer_size 400M;

	location /nextcloud/  {
		rewrite ^/nextcloud/(.*)$ /$1 break;
		proxy_pass http://0.0.0.0:8080;
		proxy_set_header Host $host;
	    	proxy_set_header X-Real-IP $remote_addr;
    		proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    		proxy_set_header X-Forwarded-Proto $scheme;
	} 
...

[alainm23]

@EthanLatimerGB I would understand that your caldav url is this right?
https://domain.name.com/nextcloud/remote.php/dav/
I will make the adjustment as Planify does not take into account the path of the url.

[EthanLatimerGB]

@EthanLatimerGB I would understand that your caldav url is this right? https://domain.name.com/nextcloud/remote.php/dav/ I will make the adjustment as Planify does not take into account the path of the url.

Yup, thats correct and when I resolve that hostname it shows the This is the WebDAV interface. It can only be accessed by WebDAV clients such as the Nextcloud desktop sync client. message.
Appreciate your time mate.

[alainm23]

The fix is available in v4.10.7, please wait for the update, it should arrive in a couple of hours.

[bipox]

I was affected by this bug too and this update fixed it, thank you