当前位置： 文江博客话题详情

cdn：trunk url可以下载：https：//cdn.cocoapods.org/cocoapods-version.yml响应：403

发布于 2025-01-27 20:54:01 字数 1488 浏览 1 评论 0原文

原文

如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论， 你可以免费 注册 一个本站的账号。

评论（4）

同尘 2025-02-03 20:54:01

还会遇到此错误！
在修复之前，您可以尝试绕过cdn：

运行：

pod repo remove trunk

并添加到podfile：

source 'https://cocoapods-cdn.netlify.app/'

或根本没有CDN：

source 'https://github.com/CocoaPods/Specs.git'

also getting this error!
until fixed, you can try to bypass the CDN:

run:

pod repo remove trunk

and add to Podfile:

source 'https://cocoapods-cdn.netlify.app/'

or without CDN at all:

source 'https://github.com/CocoaPods/Specs.git'
回复 原文
枉心 2025-02-03 20:54:01

目前，CloudFlare似乎存在问题，状态： https：//github.com/cocoapopodss /cocoapods/essess/11355

There seems to be a problem with CloudFlare at the moment, status: https://github.com/CocoaPods/CocoaPods/issues/11355

回复 原文
再浓的妆也掩不了殇 2025-02-03 20:54:01

我找到了一个非常适合我的临时解决方法：

source 'https://cdn.cocoapods.org/'

target '...' do
  ...
end

require 'typhoeus'
Typhoeus::Config.user_agent = 'CocoaPods'

在那之后，开始pod deCtegrate和pod install

I found a temporary workaround that worked for me very well:

source 'https://cdn.cocoapods.org/'

target '...' do
  ...
end

require 'typhoeus'
Typhoeus::Config.user_agent = 'CocoaPods'

After that start pod deintegrate and pod install

回复 原文
↙厌世 2025-02-03 20:54:01

现在应该修复。 Cloudflare似乎开始错误地将Cocoapods流量视为DDOS攻击， orta horta throx 更改一些配置以使其正常工作。引用他们在

DDOS检测是触发的，因为CDN活动仍在上升，可能会偶尔发生。现在，流量现在以更严格的规则反弹。 DDOS检测在CloudFlare中的工作方式是通过一系列可以单独调整的规则/启发式方法（这就是我在＃11355 。）

调整了一个人“关闭”之后，我们暂停了一些，以确定它是否在做出更改。看不到任何变化后，我们将所有规则/启发式都翻转为OFF

我们看到的仍然是类似的CDN流量模式，但有些流量偶尔会正确通过。这是我们接触Cloudflare支持的时候。在他们的帮助下，我们确定我们的规则可能从中央设置存储库迁移到不同的CDN边缘（例如，为简单起见，请认为每次最接近用户的服务器）使用了缓存（较旧的）设置。

这意味着某些区域没有新规则说忽略有关“允许自定义用户代理”的规则 - Cloudflare支持人们清除了缓存，现在看起来一切正常。

This should be fixed now. It seems that CloudFlare started to falsely detect CocoaPods traffic as a DDoS attack, and Orta Therox, a CocoaPods maintainer, had to change some configuration in order to get it working properly. Quoting from one of their comments on the GitHub issue:

The DDoS detection was triggered which can happen occasionally because CDN activity is still going up overall. It looks like traffic bounces over a threshold for stricter rules now. The way DDoS detection works in Cloudflare is through a series of rules/heuristics which can be individually tuned ( which is what I looked at in #11355 .)

After tuning the one people were hitting to "off", we paused a bit to determine if it was making changes. After seeing no changes, we flipped every rule/heuristic to off #11355

What we were seeing was still similar CDN traffic patterns but some traffic occasionally getting through correctly. This was when we reached out to Cloudflare support. With their help we determined that it was likely that the migration of our rules from the central settings repo to the different CDN edges (e.g. for simplicity think the servers closest to users each time) were using the cached (older) settings.

This meant some regions didn't have the new rules saying ignore the rule about 'allow the custom user-agent' - the Cloudflare support folks clears up the cache and now its looking like everything is working fine.

回复 原文
~没有更多了~

关于作者

陌路终见情

暂无简介

文章
评论
27 人气
发私信

相关话题

更多

热门标签

操作系统 程序设计 IT运维 Linux系统管理 JavaScript 服务器应用 solaris C/C++ PHP Shell BSD Vue.js aix Oracle Python HTML 系统管理 HTML5 CSS 前端
更多

推荐作者

李珊平

文章 0 评论 0

Quxin

文章 0 评论 0

范无咎

文章 0 评论 0

github_ZOJ2N8YxBm

文章 0 评论 0

若言

文章 0 评论 0

南…巷孤猫

文章 0 评论 0

更多

友情链接

文江博客
    我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站，即表示您同意使用 Cookies 和您的相关数据。
    原文