On Mon, Sep 21, 2015 at 1:22 PM, Jose Kahan <jose.kahan@w3.org> wrote:
> If there's no other available solution at the moment that fixes
> firefox's behavior, we'll have to roll-back.
>
Hi Jose!
It looks like you've rolled things back. I still don't understand what you
need in order to roll things out again.
Can you help me understand your expectations around HSTS and
`upgrade-insecure-requests`? In particular, it's not at all clear to me
what was happening in Firefox that wasn't happening in other browsers that
don't support the header (which, presumably, you also want to support on
the website).
-mike