I have been using Fiddler on my PC while sending traffic to it from my phone (Android 4.4.4). I can see all non-SSL and SSL traffic from our website within Fiddler, with no issues.
When I load our mobile app, however (which is partly-native and partly a wrapper for some parts of our mobile site), many (most) non-SSL pages are causing 400's (only through Fiddler).
Fiddler Log show these type of errors when it happens:
15:36:11:3018 [Fiddler] No HTTPS request was received from (chrome:6192) new client socket, port 58271.
In the raw requests for these it shows a simple GET to our website http://www.foo.com/ but the pages I am trying to visit are not the homepage, so I am not sure how it's munging up the requests. The actual homepage is http://m.foo.com/m/e/digital/index.jsp and those are loading fine.
Auto-Responder is disabled and I am doing no other re-writing that I can see, with the requests.
I have been able to reproduce this on multiple networks.
I cannot recreate the issue in other proxy tools.
Let me know if there is any more information I can provide which may help me get assistance
When I load our mobile app, however (which is partly-native and partly a wrapper for some parts of our mobile site), many (most) non-SSL pages are causing 400's (only through Fiddler).
Fiddler Log show these type of errors when it happens:
15:36:11:3018 [Fiddler] No HTTPS request was received from (chrome:6192) new client socket, port 58271.
In the raw requests for these it shows a simple GET to our website http://www.foo.com/ but the pages I am trying to visit are not the homepage, so I am not sure how it's munging up the requests. The actual homepage is http://m.foo.com/m/e/digital/index.jsp and those are loading fine.
Auto-Responder is disabled and I am doing no other re-writing that I can see, with the requests.
I have been able to reproduce this on multiple networks.
I cannot recreate the issue in other proxy tools.
Let me know if there is any more information I can provide which may help me get assistance