Update GCSE CS blog

This commit is contained in:
Matthew Grove
2018-12-08 15:14:18 +00:00
parent 3f7f4ee573
commit f675b0d9c7
4 changed files with 21 additions and 54 deletions

View File

@@ -1,6 +1,10 @@
/* Reading School 2018, CSS*/ /* Reading School 2018, CSS*/
.carousel-inner { .carousel-inner {
height: 250px; height: 250px;
border-radius: 4px;
overflow: hidden auto;
margin-bottom: 15px;
background: rgba(10,10,10,0.2);
} }
.carousel-inner .item { .carousel-inner .item {
height: 100%; height: 100%;
@@ -28,6 +32,11 @@
min-height: 32px; min-height: 32px;
} }
/* revert changes made by Bootstrap */
p {
margin: 0;
}
/* add side margins depending on screen size */ /* add side margins depending on screen size */
#main-content { #main-content {
text-align: left; text-align: left;

View File

@@ -1,19 +1,5 @@
<!-- Reading School 2018, HTML page by Matthew Grove, Year 10 --> <!-- Reading School 2018, HTML page by Matthew Grove, Year 10 -->
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, minimum-scale=1.0">
<!-- styles -->
<!-- <link rel="stylesheet" type="text/css" href="../css/pages.css"> -->
<!-- scripts -->
<!-- <script type="text/javascript" src="../scripts/scripts.js"></script> -->
</head>
<body>
<h1>Cookies</h1> <h1>Cookies</h1>
<p>
Cookies are not, unfortunately, the treats made of dough. They are, in fact, small text files, usually one-line long, which store relevant information about websites visited by a computer. This might include a selected language, or ad preferences. Some websites even use cookies to store passwords that are set to remember. Thus cookies need a lot of security and the id of each one must be unfathomably difficult to find without permission so that hackers cannot find someones cookie. Cookies are stored on the computer, as opposed to the website. Whenever you visit a browser, the browser accesses the relevant cookie and your information is there. Also, whenever a website uses cookies, they must announce the fact and give an option to refuse them, for data privacy/security reasons. Cookies are not, unfortunately, the treats made of dough. They are, in fact, small text files, usually one-line long, which store relevant information about websites visited by a computer. This might include a selected language, or ad preferences. Some websites even use cookies to store passwords that are set to remember. Thus cookies need a lot of security and the id of each one must be unfathomably difficult to find without permission so that hackers cannot find someones cookie. Cookies are stored on the computer, as opposed to the website. Whenever you visit a browser, the browser accesses the relevant cookie and your information is there. Also, whenever a website uses cookies, they must announce the fact and give an option to refuse them, for data privacy/security reasons.
</body> </p>
</html>

View File

@@ -1,19 +1,5 @@
<!-- Reading School 2018, HTML page by Matthew Grove, Year 10 --> <!-- Reading School 2018, HTML page by Matthew Grove, Year 10 -->
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, minimum-scale=1.0">
<!-- styles -->
<!-- <link rel="stylesheet" type="text/css" href="../css/pages.css"> -->
<!-- scripts -->
<!-- <script type="text/javascript" src="../scripts/scripts.js"></script> -->
</head>
<body>
<h1>HTTP</h1> <h1>HTTP</h1>
<p>
HTTP is Hypertext Transfer (or Transport) Protocol, the underlying data transfer protocol used on the World Wide Web. It defines what actions web servers and browsers should take in response to commands. For example, when a URL is opened or hyperlink (which is a URL) clicked, your web browser actually sends an HTTP request to the server which hosts the website you're trying to access, in order to fetch it and display it on your screen. Obviously, for each web server to understand these requests, the server and request must both follow this protocol. HTTP is Hypertext Transfer (or Transport) Protocol, the underlying data transfer protocol used on the World Wide Web. It defines what actions web servers and browsers should take in response to commands. For example, when a URL is opened or hyperlink (which is a URL) clicked, your web browser actually sends an HTTP request to the server which hosts the website you're trying to access, in order to fetch it and display it on your screen. Obviously, for each web server to understand these requests, the server and request must both follow this protocol.
</body> </p>
</html>

View File

@@ -1,19 +1,5 @@
<!-- Reading School 2018, HTML page by Matthew Grove, Year 10 --> <!-- Reading School 2018, HTML page by Matthew Grove, Year 10 -->
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, minimum-scale=1.0">
<!-- styles -->
<!-- <link rel="stylesheet" type="text/css" href="../css/pages.css"> -->
<!-- scripts -->
<!-- <script type="text/javascript" src="../scripts/scripts.js"></script> -->
</head>
<body>
<h1>HTTPS</h1> <h1>HTTPS</h1>
<p>
HTTPS is the secure hypertext transfer protocol, which means that it is a variation on the HTTP protocol - except it uses a secure socket layer (SSL), which is an encryption protocol invoked by an HTTPS request. SSL is essentially the usage of digital passports, and it functions by hopping onto TCP protocols. It does not resend lost packets or miscommunicated' data, because this increases security. HTTPS is the secure hypertext transfer protocol, which means that it is a variation on the HTTP protocol - except it uses a secure socket layer (SSL), which is an encryption protocol invoked by an HTTPS request. SSL is essentially the usage of digital passports, and it functions by hopping onto TCP protocols. It does not resend lost packets or miscommunicated' data, because this increases security.
</body> </p>
</html>