Kuigi paljud meist tunnevad erinevaid sadamaid, mis on määratud konkreetsetele eesmärkidele või kasutusotstarvetele, ei pruugi me teada, millist konkreetset põhjust nad valiti. Tänane SuperUseri Q & A postitus on vastuseid uudishimulike lugejate küsimustele.
Tänane küsimuste ja vastuste seanss jõuab meile viisakalt SuperUserini - Stack Exchange'i ja kogukonnapõhiste Q & A veebisaitide rühmitusse.
Photo courtesy of Rodney Lewis (Flickr).
Küsimus
SuperUseri lugeja Samuel Alexander tahab teada saada, miks 80 ja 443 olid HTTP- ja HTTPS-i vaikeseadetena valitud:
Why was port 80 chosen as the default HTTP port and 443 as the default HTTPS port? Is there any particular reason or was it just defined that way?
Miks valiti 80 ja 443 vaikimisi HTTP ja HTTPS-porti?
Vastus
SuperUseri kaasautor jcbermu vastab meile:
The Internet Assigned Numbers Authority (IANA) is a department of ICANN, a non-profit private corporation that oversees global IP address allocation, the Domain Name System (DNS), well-known ports, and other Internet Protocol-related symbols and numbers.
During March of 1990, they published a document (RFC 1060) where they listed all the well-known ports at that time. In that list there was no protocol assigned to port 80 (it jumped from 79 to 81):
At that time, port 80 was officially free. In 1991, Tim Berners-Lee issued the first version of HTTP in a document (HTTP 0.9) where he stated:Then in July of 1992, RFC1060 was made obsolete by a new document (RFC 1340) where the following appeared:That document made 80 the official port for HTTP (www). However there is nothing about port 443 in that document. During October of 1994, RFC 1700 was published and this appeared for the first time:It seems it was solicited by Kipp E.B. Hickman, who at the time worked at Mosaic, the first GUI browser company that later went on to become Netscape. It is not clear why port 443 was chosen. However, the previous RFC document had a gap from 374 through 512, but in RFC1700 the space from 375 to 451 was filled. It is most likely that the numbers were simply given in order of request.
Kas teil on seletamiseks midagi lisada? Helistage kommentaarides. Kas soovite lugeda rohkem vastuseid teistelt tech-savvy Stack Exchange'i kasutajatelt? Tutvu täieliku arutelu teemaga siit.
Pidevate julgeolekuohtudega, millega me iga päev Interneti sirvimise ajal silmitsi seisame, maksime nii palju kui võimalik. Seda silmas pidades, kuidas üritab Google Chrome'i HTTPS-i igal ajal kasutada? Tänane SuperUseri Q & A postitus räägib mõnest lahendusest, mis aitab turvatundlikul lugejal saada HTTPSi rahulolu.
Esimene ID, mida te kasutate, on selle vaikimisi olev Live ID ja seda kasutatakse teie Windowsi telefoni funktsioonide nagu Marketplace, Xbox LIVE ja Zune Pass juurdepääsustamiseks.
HTTP evolutsioon, kuidas HTTPS toimib, ja erinevus HTTP ja HTTPS-i vahel lihtsates terminites. Arutatud on Secure Socket Layer'i HTTP Vs HTTPS või Hypertext Transfer Protocol.
Router Vaikimisi parool võimaldab leida vaikimisi ruuteri kasutajanime, parooli ja sisselogimise URL-i. Hankige ruuteri juhtpaneeli URL-id, kasutades Windowsi jaoks ruuteri vaikese parooli. See toimib nagu ruuteri parooli leidja Windows 10/8/7 jaoks.
Select After The Closing Current on Firefoxi lisandmoodul, mis aitab määrata, milline vahekaart valida pärast aktiivse vahekaardi sulgemist. See aitab teil sulgeva vahekaardi töötlemise reegleid muuta.
