HSTS preload list removals for Chrome 58.

HSTS preload list removals for Chrome 58.

safic.net:
> • [oakwood] - audio stream server will not properly support https, oversite on
>   configuration preload and subdomains have been removed from headers.

medwayindia.com:
> We cannot support HTTPS on domain and we are removing it since our website
> provides only information and doesn't have payment or login functions that
> would require SSL.
>
> It was a mistake installing SSL which is not actually required by our static
> information purpose website.

sangwon.org:
> My blog service cannot support https

whiskeyriver.co.uk:
>  the reason for this is that I have recently taken over this domain, which I
>  have since discovered used to go to an https and is preloaded into the HSTS
>  list, but my brand new [and far superior] band website is created by Weebly,
>  http only and therefore will not work using this domain [it has been the
>  band’s domain for the last 9 years]. To add SSL to my new site so it will
>  work would cost more than the band can afford and so I am humbly asking if
>  you could remove it

jf.duckdns.org:
> This website is a dynamic DNS site hosted on my Raspberry Pi... I was just
> testing SSL on my site and enabled HSTS (recommended by ssllabs site tester)
> without being fully aware of the implications.  I have since removed this
> header in my apache conf however as you can see it's in the Chrome preload
> list.

avril4th.com:
> *.avril4th.com - This is blog which I take care of. However, it was moved to a
> naver blog (I was against that, but it's not my decision), which does not
> support https. At all.

builtritetrailerplans.com:
> No longer have ssl on [builtritetrailerplans.com] we have moved to
> builtritetrailerplans.com.au

x-case.de:
> [Subdomain with] Local SAP System with public DNS

BUG=655854
TBR=palmer@chromium.org

[lgarron, 2017-02-03 01:34:19]

Description was changed from

==========
sue # Enter a description of the change.
HSTS preload list removals for Chrome 58.

safic.net:
> • [oakwood] - audio stream server will not properly support https, oversite on
>   configuration preload and subdomains have been removed from headers.

BUG=655854
==========

to

==========
HSTS preload list removals for Chrome 58.

safic.net:
> • [oakwood] - audio stream server will not properly support https, oversite on
>   configuration preload and subdomains have been removed from headers.

BUG=655854
==========

[lgarron, 2017-03-02 03:23:43]

Description was changed from

==========
HSTS preload list removals for Chrome 58.

safic.net:
> • [oakwood] - audio stream server will not properly support https, oversite on
>   configuration preload and subdomains have been removed from headers.

BUG=655854
==========

to

==========
HSTS preload list removals for Chrome 58.

safic.net:
> • [oakwood] - audio stream server will not properly support https, oversite on
>   configuration preload and subdomains have been removed from headers.

BUG=655854

Review-Url: https://codereview.chromium.org/2649223002 .
Cr-Commit-Position: refs/heads/master@{#454161}
Committed:
https://chromium.googlesource.com/chromium/src/+/a739725e13c66cd34417847fb9f4...
==========

[lgarron, 2017-03-02 03:23:48]

Committed patchset #6 (id:90001) manually as
a739725e13c66cd34417847fb9f4a08854a5902f.

[lgarron, 2017-03-02 03:30:45]

Description was changed from

==========
HSTS preload list removals for Chrome 58.

safic.net:
> • [oakwood] - audio stream server will not properly support https, oversite on
>   configuration preload and subdomains have been removed from headers.

BUG=655854

Review-Url: https://codereview.chromium.org/2649223002 .
Cr-Commit-Position: refs/heads/master@{#454161}
Committed:
https://chromium.googlesource.com/chromium/src/+/a739725e13c66cd34417847fb9f4...
==========

to

==========
HSTS preload list removals for Chrome 58.

safic.net:
> • [oakwood] - audio stream server will not properly support https, oversite on
>   configuration preload and subdomains have been removed from headers.

medwayindia.com:
> We cannot support HTTPS on domain and we are removing it since our website
> provides only information and doesn't have payment or login functions that
> would require SSL.
>
> It was a mistake installing SSL which is not actually required by our static
> information purpose website.

sangwon.org:
> My blog service cannot support https

whiskeyriver.co.uk:
>  the reason for this is that I have recently taken over this domain, which I
>  have since discovered used to go to an https and is preloaded into the HSTS
>  list, but my brand new [and far superior] band website is created by Weebly,
>  http only and therefore will not work using this domain [it has been the
>  band’s domain for the last 9 years]. To add SSL to my new site so it will
>  work would cost more than the band can afford and so I am humbly asking if
>  you could remove it

jf.duckdns.org:
> This website is a dynamic DNS site hosted on my Raspberry Pi... I was just
> testing SSL on my site and enabled HSTS (recommended by ssllabs site tester)
> without being fully aware of the implications.  I have since removed this
> header in my apache conf however as you can see it's in the Chrome preload
> list.

avril4th.com:
> *.avril4th.com - This is blog which I take care of. However, it was moved to a
> naver blog (I was against that, but it's not my decision), which does not
> support https. At all.

builtritetrailerplans.com:
> No longer have ssl on [builtritetrailerplans.com] we have moved to
> builtritetrailerplans.com.au

x-case.de:
> [Subdomain with] Local SAP System with public DNS

BUG=655854
TBR=palmer@chromium.org
==========