Hi Eric, All may not be well after all: I was having a hard time clearing omniti.com from my Chrome's local HSTS list... turns out omniti.com is hard-coded in Chromium(!).
https://chromium.googlesource.com/chromium/src/+/41f8478faaf6c41b2b484e167b3dbb6a95674839/net/http/transport_security_state_static.json#5796 I suspect somebody submitted omniti.com via https://hstspreload.appspot.com/ . 2016-04-25 21:16 GMT+02:00 Eric Sproul <eric.spr...@circonus.com>: > On Mon, Apr 25, 2016 at 2:55 PM, Jacob Vosmaer <cont...@jacobvosmaer.nl> > wrote: > > Thanks Eric! > > > > It seems like I accidentally took this thread off-list. I think the > summary > > for everyone else is: HSTS on omniti.com accidentally trickled down to > > omnios.omniti.com, affecting visitors who loaded up omnios.omniti.com at > > just the right (wrong) time. HSTS headers should have been fixed now. > > Thanks for the summary Jacob-- can you confirm that you're no longer > seeing the issue? If so, we can call this one "explained". :) > > Eric >
_______________________________________________ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
