Try it on paper first. A hint, the key idea and the worked solution are here when you need them.
A small club sets up a website. Members log in with a username and a password. The login page has the URL http://www.example.com/login.html.
HTTP is the set of rules for sending web pages between a web server and a browser: the browser sends a request, and the server sends a response with the page in HTML. HTTPS is HTTP with the data encrypted, using the secure socket layer (SSL) protocol. A browser renders HTML and displays pages; it also keeps bookmarks, history and cookies, and gives tabs, navigation tools and an address bar. Each file of a page needs its own request, so
Have you tried it?
Work it out on paper first. It is fine to get stuck or make a mistake: that is how we learn. When you are ready, go through the solution one step at a time, and check each step against your own.
(a) The browser puts the password into an HTTP request. With HTTP the request is not encrypted, so it travels as plain text. Anyone who intercepts the data on the way can read the password.
(b) With HTTPS the browser and the web server use the secure socket layer (SSL) protocol. They agree on how to encrypt the data before anything is sent. The password then travels encrypted. A person who intercepts it sees only data that makes no sense without the key. The web server also shows a digital certificate, so the browser knows it is the real club website.
(c) The URL begins with https, and most browsers show a padlock in the address bar.
Watch out. HTTPS protects data on its way. It does not prove that a website is honest, so you still check the URL.
Log in to join the discussion.
Loading…