Re: Clear-Site-Data header support

Eric, thank you! I know in the past MS communicated implementation for
headers like Content Security Policy using the Edge Developer Blog (
https://blogs.windows.com/msedgedev ). Assuming Edge does plan to implement
Clear-Site-Data in the future, do you believe implementation in Edge would
be announced there too? Is that the best way to be notified?



On Wed, Sep 12, 2018 at 4:55 PM Eric Lawrence <Eric.Lawrence@microsoft.com>
wrote:

> Edge has not begun implementation of Clear-Site-Data; the feature will not
> be present in the upcoming fall release.
>
>
>
> -Eric Lawrence
> Microsoft Edge
>
>
>
> *From:* Caleb Queern <cqueern@gmail.com>
> *Sent:* Tuesday, September 11, 2018 4:45 PM
> *To:* wilander@apple.com
> *Cc:* public-webappsec@w3.org
> *Subject:* Re: Clear-Site-Data header support
>
>
>
> John, understood, and thank you! I will make a note to check back on the
> site regularly to see if CSD moves into "Under Consideration", etc.
>
>
>
> If anyone can comment for Microsoft Edge, it would be appreciated.
>
>
>
> On Tue, Sep 11, 2018 at 3:33 PM John Wilander <wilander@apple.com> wrote:
>
> On Sep 11, 2018, at 1:17 PM, Caleb Queern <cqueern@gmail.com> wrote:
>
>
>
> Hi John, good to hear from you and thanks - I knew those weren't the right
> places and appreciate you sharing the canonical source!
>
>
>
> Are you aware of any plans for Webkit to support Clear-Site-Data in the
> future?
>
>
>
> We typically don’t comment on future plans. But the WebKit Status page
> will say “Under Consideration,” “In Development,“ “Supported In Preview,”
> and “Supported” accordingly. In rare cases, an engineer might have started
> development without bumping the feature’s status yet.
>
>
>
>    Regards, John
>
>
>
>
>
> On Tue, Sep 11, 2018 at 2:18 PM John Wilander <wilander@apple.com> wrote:
>
> Hi Caleb Queern!
>
>
>
> On Sep 11, 2018, at 12:06 PM, Caleb Queern <cqueern@gmail.com> wrote:
>
>
>
> Hello WebAppSec Team,
>
>
>
> Hoping to clarify browser support for Clear-Site-Data header.  As of this
> writing here's what I believe to be true.
>
>
>
> Chrome
>
> - support: as of Chrome 61
>
> - source: https://www.chromestatus.com/feature/4713262029471744
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.chromestatus.com%2Ffeature%2F4713262029471744&data=02%7C01%7CEric.Lawrence%40microsoft.com%7Cb45f4c62a7294a2cfd7d08d618301a6b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636722992213896144&sdata=dbqIY8tynl9Xbfr7dJXd9W3BOpMFMby79gHiSH5Od%2Fg%3D&reserved=0>
>
>
>
> Firefox
>
> - support: as of Firefox 63 (shipping in October 2018)
>
> - source: Dan Veditz' email on this distro on July 20, 2018 (thx Dan!)
>
>
>
> Safari
>
> - support: "No public signals"; didn't find anything definitive from the
> Safari team
>
> - sources: https://www.chromestatus.com/feature/4713262029471744
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.chromestatus.com%2Ffeature%2F4713262029471744&data=02%7C01%7CEric.Lawrence%40microsoft.com%7Cb45f4c62a7294a2cfd7d08d618301a6b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636722992213906153&sdata=mLhrvEaKH6ESL3mPmfkmr7NzPO%2FPm98Z8NaAwsl5Y58%3D&reserved=0>
> and
> https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Clear-Site-Data#Browser_compatibility
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdeveloper.mozilla.org%2Fen-US%2Fdocs%2FWeb%2FHTTP%2FHeaders%2FClear-Site-Data%23Browser_compatibility&data=02%7C01%7CEric.Lawrence%40microsoft.com%7Cb45f4c62a7294a2cfd7d08d618301a6b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636722992213906153&sdata=tCPcgUSDGEkBpBbBFieu9IA3JF33Cx4vBOImBs%2FArPg%3D&reserved=0>
>
>
>
> WebKit's official feature status is not found on chromestatus.com
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fchromestatus.com%2F&data=02%7C01%7CEric.Lawrence%40microsoft.com%7Cb45f4c62a7294a2cfd7d08d618301a6b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636722992213916157&sdata=El9RmAzV9sFA507Oc8bzVh65tY7F22JzsddARGh%2FtwM%3D&reserved=0>
> or mozilla.org
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmozilla.org%2F&data=02%7C01%7CEric.Lawrence%40microsoft.com%7Cb45f4c62a7294a2cfd7d08d618301a6b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636722992213926169&sdata=EQIkCMFOVyVXnifavR0PCBNYcnQeECV34ddz5pHklUc%3D&reserved=0>,
> but here: https://webkit.org/status/
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwebkit.org%2Fstatus%2F&data=02%7C01%7CEric.Lawrence%40microsoft.com%7Cb45f4c62a7294a2cfd7d08d618301a6b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636722992213926169&sdata=L8gDqXdDFKmfOU0n0xH41kdRMt9NfAzZelehoMLH8L0%3D&reserved=0>
> 😉
>
>
>
> WebKit does not support Clear-Site-Data as of now.
>
>
>
>    Regards, John
>
>
>
> Edge
>
> - support: "Public support", though I didn't come across anything
> definitive from the Edge team
>
> - sources: https://www.chromestatus.com/feature/4713262029471744
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.chromestatus.com%2Ffeature%2F4713262029471744&data=02%7C01%7CEric.Lawrence%40microsoft.com%7Cb45f4c62a7294a2cfd7d08d618301a6b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636722992213936174&sdata=zOuV4BIl9iGCqplQaGflKb6b4s3jNh2jMxe8EaFvxEc%3D&reserved=0>
> and
> https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Clear-Site-Data#Browser_compatibility
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdeveloper.mozilla.org%2Fen-US%2Fdocs%2FWeb%2FHTTP%2FHeaders%2FClear-Site-Data%23Browser_compatibility&data=02%7C01%7CEric.Lawrence%40microsoft.com%7Cb45f4c62a7294a2cfd7d08d618301a6b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636722992213936174&sdata=C5Puz3QZ2CdS8gdQXFiMM%2BY13PKwxPYDbo0XNSQS%2FZE%3D&reserved=0>
>
>
>
> Would particularly appreciate any info from the Safari and Edge folks on
> the list here.
>
>
>
> Much appreciated,
>
> Caleb Queern
>
>
>
>
>
>
> --
>
> Caleb
>
> 571-228-8011
>
>
>
>
>
>
> --
>
> Caleb
>
> 571-228-8011
>


-- 
Caleb
571-228-8011