Tags UI is being affected by the new throttle rates.

[albertisfu]

Describe the issue.

Similarly to the issue that @nadahlberg found with the webhooks UI in #7340 (comment)

There is a similar issue with the Tags UI, which also uses the API internally to function. The new throttle rates can affect this frontend page quite easily after browsing a few tags.

We should remove or increase the throttle for the Tags API endpoint used by the UI.

The solution might be a bit more complex than for the webhooks endpoint since this endpoint is publicly available apart from its internal usage. Maybe we can do something like bypassing the throttle when the endpoint is called using Session Auth, while keeping the throttles in place when called using Token Auth.

Related Issue

No response

Screenshots

No response

What type of issue is this?

To Do

[mlissner]

Maybe we can do something like bypassing the throttle when the endpoint is called using Session Auth, while keeping the throttles in place when called using Token Auth.

That feels like a good fix for Nathan's bug too, yeah? If so, seems worth doing in a few select places?

[albertisfu]

That feels like a good fix for Nathan's bug too, yeah? If so, seems worth doing in a few select places?

We'll for the webhooks bug that Nathan found, the fix I think is a bit simpler since the webhooks endpoint is not public. We can just grant access to it via Session auth using:

authentication_classes = [ReplicaRoutingSessionAuthentication]

And disable throttles completely:

throttle_classes = []

[mlissner]

Alberto, as a quick fix, can/should we just remove throttles on this until we can do it properly? I doubt that'll cause many problems, but it should fix the website in the meantime?

[albertisfu]

@mlissner Yeah, we can remove the throttles from this endpoint completely or Eduardo suggested that using a scope would work too. That should fix the problem, and then we can apply final solution for the public and internal usage of this endpoint in next sprint.

In the meantime, we'll apply this temporary fix.

[ERosendo]

We’ve added a temporary fix in #7400. I’m moving this issue back to the F column for review in the next sprint.