Retry-After header not exposed for browser only applications
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The Retry-After header, which is provided for 429 (Too many requests) responses is not accessible for browser only applications. The 'Access-Control-Expose-Headers: Retry-After' is missing (at least for the /recommendations endpoint) which makes it not possible to access the Retry-After header in javascript running in the browser. Please fix this, people don't want to proxy all their requests just so they can configure CORS and work around issues in the Spotify Web API.
Labels:
- Labels:
-
Feature Request
-
Possible Bug
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page