Question: HTTPS everywhere...problem

[Zachary Yaro]

Oh, fair point.

Zachary Yaro

On Sat, Aug 4, 2018, 18:50 Peter Jaszkowiak <p.jaszkow at gmail.com> wrote:

> All of those are browser, not ES, apis.
>
> On Sat, Aug 4, 2018, 16:47 Zachary Yaro <zmyaro at gmail.com> wrote:
>
>> I am not sure off the top of my head which officially require it in the
>> spec, but I know a lot of more recent APIs, including service worker, push
>> notifications, and geolocation, require HTTPS in some or all modern
>> browsers, and I know at least the Chrome team plans to require HTTPS for
>> more APIs in the future.
>>
>> Zachary Yaro
>>
>> On Sat, Aug 4, 2018, 18:08 Claude Pache <claude.pache at gmail.com> wrote:
>>
>>>
>>> Le 4 août 2018 à 22:22, Felipe Nascimento de Moura <
>>> felipenmoura at gmail.com> a écrit :
>>>
>>> I know of (and I also support) the HTTPS everywhere campaign.
>>>
>>>
>>> I don’t think that ECMAScript has any feature related to the http
>>> protocol, or that make a distinction between secure and non-secure
>>> contexts. Wrong mailing list?
>>>
>>> —Claude
>>> _______________________________________________
>>> es-discuss mailing list
>>> es-discuss at mozilla.org
>>> https://mail.mozilla.org/listinfo/es-discuss
>>>
>> _______________________________________________
>> es-discuss mailing list
>> es-discuss at mozilla.org
>> https://mail.mozilla.org/listinfo/es-discuss
>>
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20180804/b4b11987/attachment.html>