Thread Info
  • State Not Answered
  • Replies 3 replies
  • Subscribers 2 subscribers
  • Views 6961 views
  • Users 0 members are here
Options
Suggested

Proxy error in transparent mode

JackHollister

Hi,

Each time I'm trying to access various Apple services (App Store on iOS, iCloud system settings on MAC OSX) I get log entries in webprotection log similar to this:

2016:03:07-12:23:52 firewall httpproxy[5379]: id="0003" severity="info" sys="SecureWeb" sub="http" request="(nil)" function="read_request_headers" file="request.c" line="1576" message="Read error on the http handler 110 (Input/output error)"

Because theres no URL logged within this error, I'm not able to setup an exception for that.

Firmware version: 9.375-5, software install.

Is it a bug within the proxy module?

Cheers, Jack



  • 0

    Hi,

    just wanted to add that same error occurs in version 9.355-1.1.

    Cheers, Jack

  • 0 in reply to JackHollister

    Hi there,

    this behavior occurs in all V9 Releases with enabled full https inspection.

    As a workaround you should create a testing proxy profile without https inspection. If you add a testclient into this profile you can see the request.

    Alternativly, configure default proxy in WLAN settings on ios device. If you have a mobile management solution like sophos mobile control you can push the proxy configuration.


    Regards

    mod

  • 0 in reply to mod2402

    Hi,

    I would like to add a bit more confusion here....

    Symptom: opening app store on any iOS device shows tabs "featured", "topcharts", "explore" and "search" as a blank screen, while update tab presents installed and updatable apps. At the same time the above mentioned error is logged:

    firewall httpproxy[5379]: id="0003" severity="info" sys="SecureWeb" sub="http" request="(nil)" function="read_request_headers" file="request.c" line="1576" message="Read error on the http handler 110 (Input/output error)


    Not surprisingly when disabling SSL scanning (based on client IP exception) the app store works as expected. But what would you expect as result when enabling SSL scanning again? The app store is still functional and no error is logged by httpproxy.... Weird :/

    I'm not able to decrypt the HTTPS connection (due to TLS_DHE... cipher suite), but I would bet on a mututal authentication with a kind of cookie stored on the device for future connections.

Unfiltered HTML