Activity

1. Krinkle commented on Feb 4, 2020

   

   Krinkle

   on Feb 4, 2020

   Last edited by Krinkle

   More actions

   It looks like the www.opensearch.org (redirect) supports HTTPS, but it has two issues currently:

   1. It is a self-signed certificate.
   2. It expired 3 years ago (in 2017).

   Perhaps Let's Encrypt could be used here.

   👍React with 👍1Reacted by Richie Khoo
2. dewitt commented on Feb 5, 2020

   

   dewitt

   on Feb 5, 2020

   OwnerAuthor

   More actions

   That's a good catch, and we may be able to fix it, too. Though this issue was specifically about updating the specs to use HTTPS. I'll change the title of the issue to clarify. Thanks!
3. dewitt

   changed the title [-]Update all example URLs to HTTPS[/-] [+]Update all example URLs in the specifications to HTTPS[/+] on Feb 5, 2020
4. beedell-roke commented on Sep 27, 2021

   

   beedell-roke

   on Sep 27, 2021

   Last edited by beedell-roke

   More actions

   http://github.com/dewitt/opensearch/issues/22#issue-553045623

   http://datatracker.ietf.org/doc/html/rfc3986#section-4.2 may be preferrable, because none of this is necessarily information that is requiring security during observsation of it, and cryptography is able to be greatly detrimental to anyone whose internet-connection is slow.

   However, this may only be applicable to embedded content. Thus, I am supportive of mere HTTP.
5. baby933 commented on Aug 30, 2022

   

   baby933

   on Aug 30, 2022

   More actions

   As part one of updating the OpenSearch spec to be HTTPS-only (or at least, HTTPS-strongly-preferred), update all of the example URLs to be https instead of http.

   😕React with 😕1Reacted by Mr Beedell, Roke Julian Lockhart