This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Twitter issue after enabling HTTPS scanning

I've enabled HTTPS scanning on the transparent proxy and configured the CAs for all my connected devices without too much hassle.  Everything seems to be working OK with the exception of the Twitter app for both Android & iPhone - neither of which will update the feed.  Visiting the mobile Twitter site on these devices works fine, however.

Here's an extract of the relevant Web Filtering log:

2012:10:09-07:58:34 utmfan httpproxy[12899]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0xa796bb10" function="ssl_log_errors" file="ssl.c" line="56" message="C 192.168.*.*: 4009511792:error:140940E5:SSL routines:SSL3_READ_BYTES:ssl handshake failure:s3_pkt.c:945:"
2012:10:09-07:58:34 utmfan httpproxy[12899]: id="0001" severity="info" sys="SecureWeb" sub="http" name="http access" action="pass" method="" srcip="192.168.*.*" dstip="" user="" statuscode="000" cached="0" profile="REF_DefaultHTTPProfile (Default Proxy)" filteraction=" ()" size="0" request="0xa796bb10" url="199.59.150.41" exceptions="" error=""
2012:10:09-07:58:34 utmfan httpproxy[12899]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0xc7eb7b68" function="ssl_log_errors" file="ssl.c" line="56" message="C 192.168.*.*: 3992726384:error:140940E5:SSL routines:SSL3_READ_BYTES:ssl handshake failure:s3_pkt.c:945:"
2012:10:09-07:58:34 utmfan httpproxy[12899]: id="0001" severity="info" sys="SecureWeb" sub="http" name="http access" action="pass" method="" srcip="192.168.*.*" dstip="" user="" statuscode="000" cached="0" profile="REF_DefaultHTTPProfile (Default Proxy)" filteraction=" ()" size="0" request="0xc7eb7b68" url="199.59.148.20" exceptions="" error=""
2012:10:09-07:58:34 utmfan httpproxy[12899]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x92d49f0" function="ssl_log_errors" file="ssl.c" line="56" message="C 192.168.*.*: 4001119088:error:140940E5:SSL routines:SSL3_READ_BYTES:ssl handshake failure:s3_pkt.c:945:"
2012:10:09-07:58:34 utmfan httpproxy[12899]: id="0001" severity="info" sys="SecureWeb" sub="http" name="http access" action="pass" method="" srcip="192.168.*.*" dstip="" user="" statuscode="000" cached="0" profile="REF_DefaultHTTPProfile (Default Proxy)" filteraction=" ()" size="0" request="0x92d49f0" url="199.59.150.41" exceptions="" error=""
2012:10:09-07:58:34 utmfan httpproxy[12899]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x9466340" function="ssl_log_errors" file="ssl.c" line="56" message="C 192.168.*.*: 3984333680:error:140940E5:SSL routines:SSL3_READ_BYTES:ssl handshake failure:s3_pkt.c:945:"
2012:10:09-07:58:34 utmfan httpproxy[12899]: id="0001" severity="info" sys="SecureWeb" sub="http" name="http access" action="pass" method="" srcip="192.168.*.*" dstip="" user="" statuscode="000" cached="0" profile="REF_DefaultHTTPProfile (Default Proxy)" filteraction=" ()" size="0" request="0x9466340" url="199.59.148.20" exceptions="" error="" 


Thoughts?


This thread was automatically locked due to age.
  • Well after some fiddling I found that the mobile apps use twttr.com - adding an exclusion to the web filter for twttr.com appears to have resolved the issue.
  • Spoke too soon.  Working on iPhones, NOT working on Android.  No logs are produced in Android at all in the Web Filter - but turning it off fixes the problem immediately.  

    Help?!

    EDIT: neither working, iPhone or Android.  Seems the problem is SSL-related, as the third-party Twitter apps that use OAUTH can still update feeds OK (like Echofon on iOS, for example).