Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Intermittent CloudFront 403s across auth and API endpoints

已关闭
#593 16 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
活跃
技术栈
aws
领域
api, cloud

调研方向

No repository file or test is named. Start by reviewing the CloudFront request IDs, POP, timestamps, and the App Engine-versus-local behavior, then compare the related OAuth 403 report in issue #489. Done means identifying why these requests were blocked and documenting the cause or required follow-up.

由索引模型根据 Issue 内容生成。

描述

Starting on September 30, we began experiencing intermittent CloudFront 403s across SoundCloud auth and API endpoints from our Google App Engine application. There have been three extended outages during which auth, search, and streaming requests have been affected.

I tested the same application credentials locally during the outage and all requests were succeeding with 200s. The credentials were working on App Engine until yesterday and we have not deployed any changes.

Here are some sample requests that failed on the server but are succeeding locally with the same credentials:

Timestamp: 2026-10-02 16:35:09.988845 UTC
Endpoint: GET https://api.soundcloud.com/tracks.json
HTTP status: 403
CloudFront POP: ATL59-P13
CloudFront Request ID: dA-t9MYTe_0r4NGdjfDfJ306buWaEU-D8nrjr1KTQ4bP6FRBj1GbxA==
Timestamp: 2026-10-02 16:35:10.939421 UTC
Endpoint: GET https://api.soundcloud.com/tracks/{track_id}/streams
HTTP status: 403
CloudFront POP: ATL59-P13
CloudFront Request ID: db2_u0UXpKDdZCd97pIQMeaGEBmTggFkL06heqAIHXFdxEVaQj1rPA==

Could you investigate these CloudFront request IDs and identify why the requests were blocked?

Possibly related: https://github.com/soundcloud/api/issues/489 reports a similar 403 on the OAuth token endpoint.

主要语言
JavaScript
星标
256
派生
53
平均合并
1 分钟
30 天内合并 PR
1

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

soundcloud/api 的其他 Issue

查看 soundcloud/api 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。