1f47ed1ea3
The message_bus performs a fair amount of work prior to hijacking requests this change ensures that if there is a situation where the server is flooded message_bus will inform client to back off for 30 seconds + random(120 secs) This back-off is ultra cheap and happens very early in the middleware. It corrects a situation where a flood to message bus could cause the app to become unresponsive MessageBus update is here to ensure message_bus gem properly respects Retry-After header and status 429. Under normal state this code should never trigger, to disable raise the value of DISCOURSE_REJECT_MESSAGE_BUS_QUEUE_SECONDS, default is to tell message bus to go away if we are queueing for 100ms or longer |
||
|---|---|---|
| .. | ||
| category_tag_spec.rb | ||
| email_style_spec.rb | ||
| flags_spec.rb | ||
| invite_only_registration_spec.rb | ||
| multisite_spec.rb | ||
| rate_limiting_spec.rb | ||
| same_ip_spammers_spec.rb | ||
| spam_rules_spec.rb | ||
| topic_auto_close_spec.rb | ||
| user_api_keys_spec.rb | ||
| watched_words_spec.rb | ||