3 ms·

So, Google actually appears to have capped the max_age (max max_age?) to 60 days in Chrome. Expect this in Release 51. We got into a debate with them over why

by eganist 11y ago

So, Google actually appears to have capped the max_age (max max_age?) to 60 days in Chrome. Expect this in Release 51. We got into a debate with them over why they're imposing it, but ultimately, our use case was limited and they likely had the analytics to justify capping max_age at less than a year. I think we'd still rather have had the option of allowing up to a year, but I understand the need for the gloves. https://bugs.chromium.org/p/chromium/issues/detail?id=523654 https://bugs.chromium.org/p/chromium/issues/detail?id=523654 Which gets to my point: Cyph (https://cyph.im https://cyph.im) found more utility in abusing HPKP off-label than in actually using it for its originally intended purpose, so in a roundabout way, I find myself in agreement with netcraft. Heh.

TimWolla 11y ago
I just read through the issue and then went to cyph.im to take a look myself. It fails in my Firefox because of a HPKP problem, so it seems like I accidentally deleted the cached version (or it was cleaned up automatically?). How would you solve that issue for your use case?
- buu700 11y ago
  Sorry, yeah, that is a known issue in Firefox that we're trying to have resolved; it apparently cleans up ServiceWorkers/AppCaches that haven't been actively used recently. Was this your first time opening cyph.im, or had you used it in the past?
  - TimWolla 11y ago
    I have used it in the past, that's why I assumed my cached version was cleared.
    - buu700 11y ago
      Ah, cool, that makes more sense (I couldn't think of a reason for that to possibly happen on the first use, since at that point the pinned TLS key wouldn't yet have been invalidated).