Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handle 429 HTTP response in the UI #19317

Closed
JasonMortonNZ opened this issue Jun 7, 2022 · 1 comment
Closed

Handle 429 HTTP response in the UI #19317

JasonMortonNZ opened this issue Jun 7, 2022 · 1 comment
Labels
duplicate For issues that already existed in our issue tracker and were reported previously. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.

Comments

@JasonMortonNZ
Copy link
Contributor

JasonMortonNZ commented Jun 7, 2022 •
edited

We need to adjust the UI to handle a 429 HTTP response happening. At present a generic error message will be displayed when someone encounters this issue. It would be good to implement a custom HTML error page for this response type.

This is required to complete the rate limiting feature (dev-2437) on cloud and will improve uptime, cloud performance and customer experience.
@JasonMortonNZ JasonMortonNZ added the Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc. label Jun 7, 2022
@sgiehl
Copy link
Member

sgiehl commented Jun 7, 2022

Looks like a duplicate of #19233

@sgiehl sgiehl closed this as completed Jun 7, 2022
@sgiehl sgiehl added the duplicate For issues that already existed in our issue tracker and were reported previously. label Jun 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate For issues that already existed in our issue tracker and were reported previously. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sgiehl @JasonMortonNZ