Hi Christophe, On Mon, Sep 16, 2013 at 03:05:57PM +0000, Christophe Rahier wrote: > Hi, > > It's a very strange problem. > > > Some of our users have a blank page when they try to connect to our > application but no more information (very easy to debug). > > I think it's in HTTP, not in HTTPS. > > I continue to test but I've no problem with my iPad.
What you describe sound very much like some ugly tricks that many mobile phone operators are doing (content inlining, etc...) in order to speed up page loading. Various technologies may be used, some of them might make you throw up. And that only applies to HTTP since they won't decipher HTTPS. Another important point to keep in mind is that the round trip is much longer on mobile devices than on the wired internet. So it is perfectly possible that you're observing some transfer timeouts. Checking the logs could be a good start (if one user reports a problem, try to have him check his IP address on the numerous sites that offer this service, and look for it in your logs). You'll probably not even find their faulty requests at all if it's the operator's gateways that are doing some crap. You might also have to capture the traffic and inspect it to see if you'd not be subject to request timeouts or failures to establish a TCP connection or such things (some operators apply a method known as CGN = Carrier Grade NAT which is totally incompatible with TCP stacks but they don't care, it allows them to reduce the IP address range without using proxies, and if it works for most users it's OK). Oh just one thing, are you certain that your application is not sensitive to the client's IP address ? One possible behaviour would be that clients browse via multiple gateways and that their IP address between different pages differs. Cheers, Willy
