Editing HTTPS (section)

==History==
{{Main|Transport Layer Security#History and development}}
[[Netscape Communications]] created HTTPS in 1994 for its [[Netscape Navigator]] web browser.<ref>{{cite book |url=https://books.google.com/books?id=FLvsis4_QhEC&pg=PA344 |title=Embedded Software: The Works |last=Walls |first=Colin |year=2005 |pages=344 |isbn=0-7506-7954-9 |publisher=Newnes |access-date=20 October 2018 |archive-url=https://web.archive.org/web/20190209055124/https://books.google.com/books?id=FLvsis4_QhEC&pg=PA344 |archive-date=9 February 2019 |url-status=live }}</ref> Originally, HTTPS was used with the [[Secure Sockets Layer|SSL]] protocol.<ref name=":0" /> The original SSL protocol was developed by [[Taher Elgamal]], chief scientist at [[Netscape|Netscape Communications]].<ref name="Messmer">{{cite news |last=Messmer |first=Ellen |title=Father of SSL, Dr. Taher Elgamal, Finds Fast-Moving IT Projects in the Middle East |url=http://www.networkworld.com/news/2012/120412-elgamal-264739.html |url-status=dead |archive-url=https://web.archive.org/web/20140531105537/http://www.networkworld.com/news/2012/120412-elgamal-264739.html |archive-date=31 May 2014 |access-date=30 May 2014 |work=Network World}}</ref><ref name="Greene">{{cite news |last=Greene |first=Tim |title=Father of SSL says despite attacks, the security linchpin has lots of life left |url=http://www.networkworld.com/news/2011/101111-elgamal-251806.html |url-status=dead |archive-url=https://web.archive.org/web/20140531105257/http://www.networkworld.com/news/2011/101111-elgamal-251806.html |archive-date=31 May 2014 |access-date=30 May 2014 |work=Network World}}</ref><ref name="Oppliger">{{cite book |last=Oppliger |first=Rolf |title=SSL and TLS: Theory and Practice |publisher=[[Artech House]] |year=2016 |isbn=978-1-60807-999-5 |edition=2nd |page=13 |chapter=Introduction |access-date=2018-03-01 |chapter-url=https://books.google.com/books?id=jm6uDgAAQBAJ&pg=PA15 |via=Google Books}}</ref> As SSL evolved into [[Transport Layer Security]] (TLS), HTTPS was formally specified by RFC 2818<ref>{{Cite report |url=https://datatracker.ietf.org/doc/html/rfc2818 |title=HTTP Over TLS |last=Rescorla |first=Eric |date=May 2000 |publisher=Internet Engineering Task Force |issue=RFC 2818}}</ref> in May 2000. Google announced in February 2018 that its Chrome browser would mark HTTP sites as "Not Secure" after July 2018.<ref name=":0">{{Cite web|url=https://blog.chromium.org/2018/02/a-secure-web-is-here-to-stay.html|title=A secure web is here to stay|website=Chromium Blog|archive-url=https://web.archive.org/web/20190424215132/https://blog.chromium.org/2018/02/a-secure-web-is-here-to-stay.html|archive-date=24 April 2019|access-date=22 April 2019|url-status=live}}</ref> This move was to encourage website owners to implement HTTPS, as an effort to make the [[World Wide Web]] more secure.