Changes between Initial Version and Version 1 of Ticket #915, comment 4


Ignore:
Timestamp:
10/13/16 11:38:05 (4 years ago)
Author:
Laurence 'GreenReaper' Parry

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #915, comment 4

    initial v1  
    1 This was a very confusing blocker for us on multiple attempts to update our origin to h2; Safari clients (especially on mobile devices) could not access our new files. This results in massive connection churn and increased bandwidth use as the clients retry the download, impacting us for days or weeks afterwards, as the files in question were still cached and being served with the Upgrade header.
     1This was a very confusing blocker for us on multiple attempts to update our origin to h2; Safari clients (especially on mobile devices) could not access our new files. This results in massive connection churn and increased bandwidth use as the clients retry the download, impacting us for weeks afterwards, as the files in question were still cached and being served with the Upgrade header.
    22
    33"proxy_hide_header Upgrade;" should be a default at least for cases where it includes h2 (possibly h2c?) as without it and with a HTTP/2 upgrading back-end, nginx essentially breaks for these clients.