Skip to content
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

Is webcal link a "live" link or only a copy of current state? #15967

Open
rollanders opened this issue Jun 15, 2019 · 7 comments

Comments

@rollanders
Copy link

commented Jun 15, 2019

This has been asked for many times. In the issue "Share NC Calendar with Google Calendar - No Updates! #706" it is claimed that the "https://mydomain.com/nextcloud/remote.php/dav/public-calendars/XXXXXXXXXXXXXXXX?export link is always up to date."
This may be true, but it is still an export link, which I suppose means it is not "live", ie does not provide new events.
Google claims that if there is a "prenumeration" to a link that provide "live" information it should work.
Is there any such possibility in NC? Does the webcal link provide additional live information about changes done or only a copy of the current state at the moment it was constructed?

Is your feature request related to a problem? Please describe.

  1. I create a calendar in NC. I share it with Google calendar through a webcal link. The events from the calendar appears in the Google calendar OK.
  2. I add new event to the NC calendar. I assume they should appear in the Google calender. But they do not. I have to create a new Google calendar based on a new webcal link.
  3. This issue has been discussed many times. There is a misunderstanding that the Google calendar is slow to react because of a "cache". The change does not appear.
  4. According to Google the Google calendar shoul automatically update if the webcal link is changed. I wonder if the webcal link only gives the current state and does not change when new events are added.

Describe the solution you'd like
I wouöd like the Google calendar to be synced with the NC calendar

Describe alternatives you've considered
I can do the other way - make a Google calendar that is imported to NC and that shows the new events that is added to the Google calendar. It works. But It would be better for the group if the other way around would work.

@kesselb

This comment has been minimized.

Copy link
Contributor

commented Jun 15, 2019

Would you mind to check the referenced issue again? Is "706" the right one? Looks unrelated to your question for me.

Update: nextcloud/calendar#706 looks like the right one ...

@rollanders

This comment has been minimized.

Copy link
Author

commented Jun 15, 2019

Correct it is nextcloud/calendar#706

I got an answer that this issue is related to the server and not the calendar

@kesselb

This comment has been minimized.

Copy link
Contributor

commented Jun 15, 2019

Mind to edit your initial post and use the feature request template: https://raw.githubusercontent.com/nextcloud/server/master/.github/ISSUE_TEMPLATE/Feature_request.md?

@kesselb

This comment has been minimized.

Copy link
Contributor

commented Jun 15, 2019

curl -I "https://demo.nextcloud.com/looj8eiw/remote.php/dav/public-calendars/z4sdNJW2MH33j3pW?export"

HTTP/1.1 200 OK
Date: Sat, 15 Jun 2019 13:24:47 GMT
Server: Apache
Strict-Transport-Security: max-age=15768000
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Content-Security-Policy: default-src 'none';
X-Frame-Options: SAMEORIGIN
Content-Disposition: attachment; filename="z4sdNJW2MH33j3pW-2019-06-15.ics"
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
X-Robots-Tag: none
X-Download-Options: noopen
X-Permitted-Cross-Domain-Policies: none
Referrer-Policy: no-referrer
Content-Type: text/calendar;charset=UTF-8

Compared to a calendar from another application (which works fine with google calendar):

  1. A proper expires header
  2. X-PUBLISHED-TTL:PT4H in VCALENDAR (https://stackoverflow.com/questions/538081/set-update-limits-on-icalendar-feed)

This might be a starting point for further triage ...

cc @georgehrke

@kesselb kesselb added the needs info label Jun 15, 2019

@georgehrke

This comment has been minimized.

Copy link
Member

commented Jun 15, 2019

We should probably have both. X-PUBLISHED-TTL and the new standard REFRESH-INTERVAL
https://tools.ietf.org/html/rfc7986#section-5.7

@georgehrke

This comment has been minimized.

Copy link
Member

commented Jun 17, 2019

I'm not really sure what refresh rate we should propagate. It heavily depends on the use-case.
There will be calendars updated multiple times an hour and that should at most be cached one hour.
Others are updated merely once in a couple of months and a refresh rate of one hour would just cause unnecessary load on the server.

cc @tcitworld

@georgehrke georgehrke self-assigned this Jun 21, 2019

@georgehrke georgehrke added this to the Nextcloud 17 milestone Jun 21, 2019

@nextcloud-stale

This comment has been minimized.

Copy link

commented Jul 21, 2019

This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.