Would you agree to support a track response support? about rack-attack

[zmillman]

@flevour why should this be part of rack-attack instead of a separate HTTP code-tracking Rack middleware?

[ktheory]

@flevour: Interesting. I'm hesitant to expand the track functionality to include responses. Adding tracks for requests was b/c it was such a close fit to how we're already blocking & throttling other requests.

For simplicity and focus, I'd like to keep parsing responses outside the scope of rack-attack. You could implementing response tracking as a separate middleware or gem (per @zmillman's suggesting).

[flevour]

In my case I'd want to throttle only successful requests to API over a given period.
Basically I'm re-using the whole rack-attack count-over-period logic but to throttle responses.
I see your point about simplicity/focus though, thanks for sharing your thoughts!