IOS 11 Problems

  • Apples bug but we may be seeing the problem as we have nginx in front of apache for webmeetings. You can see the HTTP/2 requests coming in from the IOS 11 phones.

    X.XXX.XXX.XXX - [20/Sep/2017:15:02:25 -0500] “POST /Microsoft-Server-ActiveSync? HTTP/2.0” 200 461 “-” “Apple-iPhone8C2/1501.372” “-”

  • It looks like the IPhones HTTP/2 SendMail request is probably malformed as it doesn’t make it though our nginx proxy to apache. The rest of the requests get converted into HTTP/1.1 and show up in the apache logs.

    In the front end nginx logs upon a failed send
    XX.XXX.XXX.XXX - [20/Sep/2017:15:26:17 -0500] “POST /Microsoft-Server-ActiveSync? HTTP/2.0” 400 220 “-” “Apple-iPhone8C2/1501.372” “-”

  • No issues to report with iOS 11 and Z-Push 2.3.8 final + nginx 1.13.5 with http2 enabled in nginx host config.

    listen fastopen=256 ssl http2;
 - [24/Sep/2017:12:34:38 +0400] “POST /Microsoft-Server-ActiveSync? HTTP/2.0” 200 0 “-” “Apple-iPhone9C3/1501.372” - [24/Sep/2017:12:34:39 +0400] “POST /Microsoft-Server-ActiveSync? HTTP/2.0” 200 25 “-” “Apple-iPhone9C3/1501.372”

  • @deisenlord Reconfiguring your apache setup to accept HTTP/2 connections should address the issue you are experiencing. HTTP/1.1 requests will still be accepted/processed by both nginx (frontend) and apache (backend)

    btw- you may want to redact your email address from your log posts.

  • This is kind of a very big bug on iOS 11. Many user have complained that they cannot send , receive, and replay from their, Office 365, or Exchange 2016 in iOS 11 Mail app on iPhone iPad, after upgrading to iOS 11. Apple official has already announced this problem and that they will team up with Microsoft to solve this iOS 11 exchange issue.
    By far, the practical solution is downloading the free Outlook for iOS client from the App Store. The Outlook for iOS client fully supports various email services, including, Office 365, and Exchange Server 2016. Hope it works for you.

    For more iOS 11 problems, you can find the answers in this page, I found it couple days ago: 37 Common iOS 11 Problems and Quick Fixes >

  • @stephenr I agree, Apple should have consulted with the concerned technology maintainers prior to enforcing http/2 for ActiveSync. However, I also commend Apple for pushing forward with the adoption of newer technologies/features. They just went about it the wrong way.

    For Z-Push users though, the recommended and working solution is to upgrade http web/proxy services to support http/2

  • Kopano

  • Banned

    This post is deleted!

  • This post is deleted!

  • Kopano

    This post is deleted!

Log in to reply