Consider allowing subscription to decide if retry should be performed or not #1970
Description
Context:
One of our users had a situation, where the subscription application could return response with status:
- 400 Bad Request
- 409 Conflict
The conflict situation was caused by eventual consistency and could be resolved automatically.
Client didn't want to retry all 4xx, as the 400 Bad Request requests were always invalid, and were slowing down the subscription. Client wanted to only retry 409 Conflict requests, as a retry on such request could result with 200 OK.
Issue:
Currently, there is no solution for the problem above, other than changing HTTP response code from 409 to 500. Scope of this task is to discuss and propose solution for this problem.