Hmm, so it must be something at a lower level in iOS.
I almost wish that I did have an iOS device so I could dig into this a bit more. I'm almost certain that it's something to do with the headers that is upsetting iOS. No doubt some "security" feature. Unfortunately, without a clear idea of what it's actually choking on, it's really hard to know how it might be worked around.
Another way to try to debug this (without using browser "web dev tools") would be to use curl from the CLI. To compare headers, get the headers from each server (use the '--insecure switch to skip checking cert validity):
It's an interesting problem that I'd really love to understand. So also allowing me to recreate it would be useful. If possible, could you share the proxy config and the backend webserver config? Also knowing what software (and versions) you're using (both the proxy and the webserver behind it) would be useful to try to recreate it.
To be clear, I'm pretty snowed under at the moment, so even if you give me all the above info, I'm not sure when I'd get to this. There is also a good chance it'll keep getting pushed down my "todo" list - so no promises...
Hmm, so it must be something at a lower level in iOS.
Hmm, so it must be something at a lower level in iOS.
I almost wish that I did have an iOS device so I could dig into this a bit more. I'm almost certain that it's something to do with the headers that is upsetting iOS. No doubt some "security" feature. Unfortunately, without a clear idea of what it's actually choking on, it's really hard to know how it might be worked around.
Another way to try to debug this (without using browser "web dev tools") would be to use curl from the CLI. To compare headers, get the headers from each server (use the '--insecure switch to skip checking cert validity):
It's an interesting problem that I'd really love to understand. So also allowing me to recreate it would be useful. If possible, could you share the proxy config and the backend webserver config? Also knowing what software (and versions) you're using (both the proxy and the webserver behind it) would be useful to try to recreate it.
To be clear, I'm pretty snowed under at the moment, so even if you give me all the above info, I'm not sure when I'd get to this. There is also a good chance it'll keep getting pushed down my "todo" list - so no promises...