+1 also encountering this error on a seemingly simple GET request. Interestingly, when I setup a proxy (Proxyman), requests from the same device succeed, then start failing again when I turn proxying off. Suggests to me it has something to do with the network connection to our specific server (i.e. the proxy tool is masking an underlying issue).
Has anyone on the thread here has success in resolving/avoiding this error?
Reading the other thread that @eskimo mentions, I notice mention of the problem starting when "servers migrated to Http2". We also similarly moved to Http2 when we introduced a caching layer in front our service. Requests direct to the underlying service don't exhibit this issue, but I'm hoping we can determine a more specific cause.