android - using self signed certificate on mobile data plan -


short story: experiencing different android app behaviors based on whether i'm on wireless or mobile data. looks related using https self signed certificate.

long story: have tomcat instance running, configured ssl connector , self signed certificate. works great. can access using https desktop , android app. android app, had use bks hold cert managed working too. problem? when switch phone mobile data, following failure:

<?xml version='1.0'?>     <!doctype html public '-//wapforum//dtd xhtml mobile 1.0//en'     'http://www.wapforum.org/dtd/xhtml-mobile10.dtd'>     <html xmlns='http://www.w3.org/1999/xhtml'>     <head>     <title>the request failed</title>     </head>     <body>     <p><big>the request not understood.</big></p>     <p>     <i>technical description:</i><br/>400 bad request - check spelling requested url</p>     </body>     </html> 

i tried access same url app request chrome running on phone, , got error:

error 111 (net::err_tunnel_connection_failed): unknown error. 

i see no issue @ if use wifi. issue reproduces consistently on mobile data. provider at&t. ideas?


Comments

Popular posts from this blog

Perl - how to grep a block of text from a file -

delphi - How to remove all the grips on a coolbar if I have several coolbands? -

javascript - Animating array of divs; only the final element is modified -