Next-gen HTTP 2.0 protocol will require HTTPS encryption (most of the time)
Source
A Guy
Sending data in plain text just doesn’t cut it in an age of abundant hack attacks and mass metadata collection. Some of the biggest names on the Web—Facebook, Google, Twitter, etc.—have already embraced default encryption to safeguard your precious data, and the next-gen version of the crucial HTTP protocol will only work for URLs protected by HTTPS.
Mark Nottingham, chair of the HTTPbis working group developing the HTTP 2.0 protocol for the Internet Engineering Task Force, made the announcement early Wednesday in a Worldwide Web Consortium mailing list.
Source
A Guy
My Computer
- Computer type
- PC/Desktop
- OS
- Windows 10 Home x64
- CPU
- INTEL Core i5-750 Quad-Core 3.37GHz
- Motherboard
- ASUS P7P55D
- Memory
- HyperX Fury Black Series 8GB (2 x 4GB) 1866Mhz
- Graphics Card(s)
- EVGA GeForce GTX 750 Superclocked 1GB 128-Bit GDDR5
- Monitor(s) Displays
- LG 32MA68HY 32" IPS
- Screen Resolution
- 1920 x 1080
- Hard Drives
- Samsung 840 Evo 120GB, SEAGATE 500GB Barracuda® 7200.12, SATA 3 Gb/s, 7200 RPM, 16MB cache
- PSU
- ANTEC TruePower New TP-550, 80 PLUS, 550W
- Case
- ANTEC Three Hundred Illusion
- Cooling
- COOLER MASTER Hyper 212 Plus, 4 x 120mm 1 x 140mm Noctua's
- Internet Speed
- 85 + Mbps
- Antivirus
- Avast
- Browser
- Vivaldi