Idea: Whitelist vs Blacklist for chain destinations.

[verahayter]

Currently the chain destination(s) field operates on a whitelist basis. It only applies the chain to specifically chosen requests.

I would propose that for each chain you can specify whether to use a whitelist or blacklist, so that we can set some chains to automatically apply to every request except specified ones. This is especially important if requests use CSRF tokens, since in most cases you want to apply these in every request. Currently when sending multiple requests to AuthMatrix, you have to go in and re-configure the chains so that the new requests are included in the destination.

Clearly some chains should still work on the whitelist method, but having a blacklist would be ideal as I find myself spending quite a bit of time re-selecting destination requests when I send new requests to AuthMatrix. This is especially time consuming if I need to apply the chain to request 1, 4-6, 7, 10-15, etc. With a blacklist I could just select requests 2-3, 5, 8-9 and leave it alone.

[vikaskope]

+1