+1 I'm also encountering an NSURLErrorCannotParseResponse 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 had success in resolving/avoiding this error?
I noted the 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. I can raise a bug for this, but I'm hoping we can determine a more specific cause and workaround for existing deployed apps.
Topic:
App & System Services
SubTopic:
General
Tags: