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

CDN support? #74

Closed
darhwa opened this issue May 23, 2020 · 10 comments
Closed

CDN support? #74

darhwa opened this issue May 23, 2020 · 10 comments

Comments

@darhwa
Copy link

darhwa commented May 23, 2020

Naiveproxy only directly serves on user's host server, but can't be fronted by CDN. CDNs don't support CONNECT method.

Would you like to extend usage scenerio of naiveproxy to cover CDN fronting? Currently I know this can be done by either websocket or using PUT/POST method to simulate a tunnel, like what v2ray does.

@klzgrad
Copy link
Owner

klzgrad commented May 23, 2020

I'm against CDN fronting. Can't think of any actual benefit with it.

@ArcCal
Copy link

ArcCal commented May 23, 2020

True server IP is hidden behind the CDN. Besides, the CDN can accelerate connection speed. These features may be very useful in China.

@klzgrad
Copy link
Owner

klzgrad commented May 23, 2020

This is assuming you're freeloading the CDN for traffic proxying, which is likely formally an abuse in their terms of use. (Domain fronting was banned from major CDNs a while ago.) And there's no shortage of CDNs being blocked either.

The only case that is favorable for the CDN's case is when you have an extremely cheap server and free CDN proxying, the combination of the two somehow is faster than the naked server. But I consider this tool high-security and not for everyone, so unless I see very convincing proof this case is actually viable I'm not invested in this.

@darhwa
Copy link
Author

darhwa commented May 29, 2020

@klzgrad @tomac4t

Thanks for clarifying. I'm new in this area and have seen the practice of CDN fronting is popular among v2ray users. Now I believe that your perspective about CDN is right.

@darhwa darhwa closed this as completed May 29, 2020
@Alvin9999
Copy link

刚刚一个vps ip被封了,套CDN在某种程度上可以防止ip被墙。

@cercveil
Copy link

cercveil commented Oct 19, 2022

说实话,不论是套cdn还是不套cdn,只要被gfw探测到,就都会产生个人利益的损失和公共利益的损失。套cdn的损失就不说了,不套cdn的情况下,要是服务器ip被封了,那毫无疑问会对下一个接手该服务器的用户产生损失,服务商可用的ip减少,对服务商也会产生损失,难道不也是一种滥用吗?
另外楼上的 CDNs would see it as abuse because the collateral damage also is unacceptable to them. 还得打个问号,像v2fly.org这种网站,cloudflare应该是知道是明确违反我们的规定的,如果cf认为v2fly.org是unacceptable,为什么不尽早把它给封了?

@cercveil
Copy link

cercveil commented Oct 26, 2022

有个人给我回了句"现在是 2022 年 10 月,对于 Cloudflare 来说:域前置并不是免费套餐内的服务,而仅仅是利用 CDN 建立隧道我并不觉得是滥用,要知道免费服务 Cloudflare Tunnel 相当于同类用途,有具体条款吗?",被删了不知道怎么回事,那我就单独再回一句。
域前置既不在免费套餐里,也不在收费套餐里,在cf的社区https://community.cloudflare.com/t/is-it-possible-to-use-a-cloudflare-service-worker-as-a-proxy-web-server/145628/6和https://community.cloudflare.com/t/could-cloudflare-support-domain-fronting/200944已明确表明域前置不受cf的支持,不知你特意提个免费套餐是什么意思。至于你说搭个隧道不算滥用,是完全回避了我特意提及v2fly的重点,要么你就是认为v2fly不算滥用,然而cf的服务条款已提到You may not to use the Websites or Online Services in any way that violates any applicable federal, state, local, or international law or regulation (including, without limitation, any laws regarding the export of data or software to and from the US or other countries).
我承认拿cloudflare来套vpn从而规避中国大陆的审查的的确确是一种滥用。但我上一条回复中关于搭建vpn对主机商是滥用的观点仍然不变,在著名主机商搬瓦工的服务条款提及到
We do not tolerate the following activities on our servers:Open proxy servers (due to abuse committed through open proxies);vultr的使用政策也提到禁止Operation of Certain Network Services. Operating network services like open proxies, open mail relays, or open recursive domain name servers.尽管proxy实际上不等于vpn,但拿来翻墙的话,vpn确实充当"代理"用户访问其他网站的用途,除外,很多vps服务商也提到不得违反你居住的地方的法律。因此,不管怎么样,搭个vpn就基本必然是滥用,对于搭建翻墙用的vpn用途友好的主机商并不算多,所以为什么还要纠结套个cdn是不是滥用呢?

@ArcCal
Copy link

ArcCal commented Oct 26, 2022

还是别连累CDN服务商了吧

@murez
Copy link

murez commented Oct 5, 2023

你的流量对于 CF 来说算不上多少

@murez
Copy link

murez commented Oct 5, 2023

另外 CF 应该是支持QUIC 和 CONNECT 的

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants