Rate limit/ Retry-After header value too large

[Yajat Grover]

Why is Atlassian rate limiting my selective requests. When I try to fetch confluence content on page using REST API, it works but when I am trying to download attachments on that page, it says Rate Limit Exceeded.

Even when I try ConfluenceLoader from LangChain it says Retry-After header value too large - OverFlow error.

This URL works:

f"{CONFLUENCE_URL}/rest/api/content?title={PAGE_TITLE}&spaceKey={SPACE_KEY}&expand=body.storage,version"

This URL of downloading attachments results in Rate Limit exceeded error:

f"{CONFLUENCE_URL}/rest/api/content/{page_id}/child/attachment"

Response headers for failed URL:

'X-RateLimit-Limit': '0', 'X-RateLimit-Remaining': '0', 'X-RateLimit-FillRate': '0', 'X-RateLimit-Interval-Seconds': '1', 'Retry-After': '9223372036854775807'

Why do I have these as headers, why is RateLimit 0, why do some endpoints work, some results in rate limit exceeded/overflow error.

Can anybody explain why is this happening? 

[Aron Gombas _Midori_]

@Yajat Grover 

Yea, rate limiting is a PITA. All app developers are fighting with them.

This is the most important related documentation: https://developer.atlassian.com/cloud/jira/platform/rate-limiting/

About why different end-points behave differently? I recall that rate limiting was introduced in multiple batches, each batch covering a selection of REST API end-point. I can even imagine that certain, less critical end-point are still not rate limited...