I tested both, with or without trailing slash. And I can now say that it doesn't work wih a trailing slash while it works like a charm without a trailing slash.
I think that could be added in the documentation as a small detail like that can stay unseen for hours... (at least it did for me!)
Ploc
Le 01/03/2018 à 08:00, Julien Métairie a écrit :
Ploc,
I think it should work with or without trailing slash.
The Wikipedia page[1] should be enough to understand how CORS works. Nevertheless, I notice that examples don't have any trailing slash...
Julien
[1] https://en.wikipedia.org/wiki/Cross-origin_resource_sharing
-------- Message original -------- Sujet : Re: [Inf-IT DAVcl] does infcloud support header "Access-Control-Allow-Origin <a-domain>"? De : Ploc pub2018@acampado.net Pour : davclients@inf-it.com Date : 01/03/2018 00:15
Thanks for your answer Julien.
I think that's what I did :
I set "https://cal.example.com/" with a trailing slash.
Then, it should work?
Le 28/02/2018 à 09:07, Julien Métairie a écrit :
Hi Ploc,
As far as I know, you need to fill Access-Control-Allow-Origin with a full URL, including the protocol. For example: Access-Control-Allow-Origin "https://cal.example.com"
Regards, Julien
Le 28/02/2018 à 00:04, Ploc a écrit :
Hi everyone,
Does infcloud support header "Access-Control-Allow-Origin <a-domain>"?
I tried to configure my caldav server with "Access-Control-Allow-Origin" header set to <a-domain>", but infcloud seems to be unable to connect the caldav server, reporting the following error in the browser's console:
"Error: [netCheckAndCreateConfiguration: 'PROPFIND
https://<a-domain>/dav/'] code: '0' status: 'error' - see https://www.inf-it.com/infcloud/readme.txt (cross-domain setup)" webdav_protocol.js:120:4
When I set this "Access-Control-Allow-Origin" header to "*", it works.
I find it more secure to be able to set this header.
Can you tell me how is infcloud supposed to work with this header?
Thank!