-
Suggestion
-
Resolution: Fixed
-
None
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
Customers often will use their Confluence as a public facing, anonymously accessible documentation source.
In these sorts of situations, Confluence can be subjected to higher than normal traffic loads. We've seen some cases in support where customer facing instances were having increased load being generated by the Quick Reload plugin - the plugin that's responsible for letting a user know when a new comment has been added to the page.
At the moment, we have two potential workarounds for dealing with this issue, however, some customers may want the functionality that Confluence provides for logged in users, while disabling it for anonymous users.
I'd like to suggest an improvement, either:
- Being able to disable this endpoint for anonymous users if required
- Being able to increase the time out between checks to the endpoint.
Either of these improvements would be a small but helpful change for customers who have their Confluence instance accessible to the public.
- relates to
-
- Closed
What was implemented, 1., 2., or both? Any links to the documentation?