将ic添加到Google日历的链接停止工作 [英] Link to add ics to Google Calendar stopped working

查看:100
本文介绍了将ic添加到Google日历的链接停止工作的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在网站上有一个链接,可让用户将ICS供稿添加到其Google日历中.使用此代码:

I have a link on a website to let users add an ICS feed to their google Calendar. Using this code:

http://www.google.com/calendar/render?cid=https://<etc>

它已经工作了3-4年,但现在已经不复存在了. Google发送给我的消息是:

It worked for 3-4 years but not anymore. The message Google sends me is:

This email address isn't associated with an active Google Calendar account: https://<etc>

如果我手动输入ics提要,则一切正常:提要已被解析.没有错误.

If I enter the ics feed manually things work ok: the feed is parsed as should. No errors.

有什么想法可以解决这个问题吗?

Any idea where to look to fix this?

推荐答案

我也有这个问题.解决了吗?

I too have this problem. Did you solve it?

我的测试表明,当使用带有 http 的URL时,它可以正常工作,例如:

My tests show that it works when using URLs with http, like:

www.google.com/calendar/render?cid=http%3A%2%2Fwww.example.com%2FCalendar%2FPublic%2520Events.ics

但是使用 https ,例如:

www.google.com/calendar/render?cid=https%3A%2%2Fwww.example.com%2FCalendar%2FPublic%2520Events.ics

我的解决方法是在链接中使用http,但将其重定向到Web服务器中的https.不是很优雅,但是可以. GET不会被加密,但至少答案是正确的.

My workaround for this is to use http in the link, but redirect it to https in the web server. Not very elegant, but it works. The GET won't be encrypted, but at least the answer is.

编辑:实际上,如果您仅通过身份验证字符串参数进行身份验证,那么通过HTTP而非HTTP发送GET可能会带来巨大的安全风险,这对于日历而言可能很难饲料.可以嗅探GET的任何人都可以自己通过https发送相同的请求.

EDIT: Actually, it can be a huge security risk sending the GET over http instead of https if you don't do any more authentication than via query string parameters, which can be hard for calendar feeds. Anyone who can sniff the GET can send the same request over https themselves.

这篇关于将ic添加到Google日历的链接停止工作的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆