UniqueKeyForRequest and POST body content
ChristopheOosterlynck opened this issue · 1 comments
RateLimitedHttpMessageHandler:UniqueKeyForRequest doesn't take into account the content of the HttpRequestMessage when it is a POST request. POST requests which are similar and just have a different content, are considered the same request and only the first one is executed when multiple of those similar POST requests are outstanding. All calls receive the same response while they should actually receive different responses.
In #6 @paulcbetts says "POST/DELETEs don't get cached or deduped", however looking at RateLimitedHttpMessageHandler doesn't seem to support this.
Requests with a body should definitely look at the body before deduplicating it. IMHO, only indeponent requests should ever be deduped. Likely, it'd simpler and "safer" to only support safe methods deduplication: GET and HEAD.