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

Repost endpoint returning HTTP 429

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

还没有人认领这个 Issue。

评估

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

调研方向

Start by comparing the reported /repost/tracks requests with the related issue 584 and reproduce the 429 response using the Swagger API explorer, multiple OAuth tokens, and separate IP addresses. Check whether the endpoint's rate-limit headers and behavior differ from other endpoints; done means identifying the cause and confirming the expected response or required API-side fix.

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

描述

As mentioned in https://github.com/soundcloud/api/issues/584:

We seem to be getting nothing but HTTP 429 on the /repost/tracks endpoint, while other endpoints from the same machine(s) work perfectly fine. That endpoint also doesn't return any information about the rate limits in the response headers, while others return:

< x-ratelimit-limit: -1
< x-ratelimit-remaining: 0
< x-ratelimit-reset: 0

An example:

< HTTP/1.1 429 Too Many Requests
< Content-Type: application/json
< Content-Length: 38
< Connection: keep-alive
< Date: Sat, 26 Sep 2026 23:00:26 GMT
< server: istio-envoy
< vary: Origin
< x-generator: tyk.io
< x-tyk-trace-id: e6413ed89739db0e19ddd99ff0e55429
< x-envoy-upstream-service-time: 2
< X-Cache: Error from cloudfront
< Via: 1.1 08dc547306e2c7102196b53ce0859e80.cloudfront.net (CloudFront)
< X-Amz-Cf-Pop: FRA60-P11
< X-Amz-Cf-Id: PfWdzKD62C4OW1IeJJFLpzHI-6tJ1FPTbatn2vexuwe4VMtZa0u6aw==

Getting the same when sending from 2 separate IP addresses, with multiple different OAuth tokens (not sure which one rate limiting is tied to).
Also getting this when trying to send a request on the Swagger test page at: https://developers.soundcloud.com/docs/api/explorer/open-api#/reposts/post_reposts_tracks__track_urn_

Image

Sent the application's Client ID to @SoundCloudDev on X.

主要语言
JavaScript
星标
259
派生
54
平均合并
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 摘要。