Rate limit headers absent?

Question

For an url like https://www.strava.com/api/v3/activities/{id}/streams?keys=time,latlng,altitude,heartrate,cadence,distance,moving,watts

I’m currently seeing the following response headers: content-type, content-length, connection, date, server, vary, x-envoy-upstream-service-time, x-cache, via, x-amz-cf-pop, and x-amz-cf-id, but *not* the rate limit headers described at https://developers.strava.com/docs/rate-limits/

What gives? Is the documentation out of date? Have the rate limit headers been deprecated? Am I seeing proxy-cached content that strips the rate limit headers or something like that? If the rate-limit headers are absent, does that mean the request doesn’t count against quotas?

Jan_Mantau · Answer

That’s weird, but at least all the other methods still have the four rate-limit entries in the result header. Proxy caches can be ruled out for dynamic data and the cloudfront result explicitly states a cache miss even for repeated uses of the same parameters.

The good thing is you are right with one assumption: The stream requests don’t count for the limits at the moment, I’m not even sure we should mention that where Strava can read it :-)

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded