HTTP or HTTP/2: Difference between revisions

Revision as of 16:47, 30 May 2018

This is student work which has not yet been approved as correct by the instructor

Case study notes^[1]

Introduction[edit]

Please write a clear, concise description of your topic here.You will likely reference your introduction from somewhere else. Please use the following syntax at the end of each of your ideas. IT IS CRITICAL YOU ATTRIBUTE others work. Your introduction should be factual. No more than 3 or 4 sentences, please. Because you are not an expert in your topic, I expect you to triangulate your information. LOTS OF LINK TO OTHER RESOURCES PLEASE! If you do not use a section, please delete it. Your finished page should only have information which explains your topic.

Hypertext Transfer Protocol is a communications protocol. It is used to send and receive webpages and files on the internet. It was developed by Tim Berners-Lee and is now coordinated by the W3C. HTTP version 1.1 is the most common used version today. It is defined in RFC 2616.^[2]

How it works[edit]

HTTP works by using a user agent to connect to a server. The user agent could be a web browser or spider. The server must be located using a URL or URI. This always contains http:// at the start. It normally connects to port 80 on a computer.

== Difference between HTTP and HTTPS

A more secure version of HTTP is called HTTPS (Hypertext Transfer Protocol Secure). This contains https:// at the beginning of the URL. It encrypts all the information that is sent and received. This can stop malicious users such as hackers from stealing the information and is often used on payment websites. HTTPS uses port 443 for communication instead of port 80^[3]

Request message[edit]

he request message contains the following:

Request line, such as GET /images/logo.gif HTTP/1.1, which requests the file logo.gif from the /images directory
Headers, such as Accept-Language: en
An empty line
An optional message body

The request line and headers must all end with two characters: a carriage return followed by a line feed, often written <CR><LF>. The empty line must consist of only <CR><LF> and no other whitespace. In the HTTP/1.1 protocol, all headers except Host are optional.

A request line containing only the path name is accepted by servers to maintain compatibility with HTTP clients before the HTTP/1.0 standard.

Pictures, diagrams[edit]

Pictures and diagrams go a LONG way to helping someone understand a topic. Especially if your topic is a little abstract or complex. Using a picture or diagram is a two part process:

External links[edit]

It would be helpful
to include many links
to other internet resources
to help fellow students
Please make sure the content is good
and don't link to a google search results, please

References[edit]

[1] ttp://www.flaticon.com/

[2] ttps://computersciencewiki.org/index.php?title=HTTP_or_HTTP/2&action=edit

[3] ttps://computersciencewiki.org/index.php?title=HTTP_or_HTTP/2&action=edit

[1]

[2]

[3]

@@ Line 16: / Line 16: @@
 --------------------------------------------
+== How it works ==
- <nowiki>
+HTTP works by using a user agent to connect to a server. The user agent could be a web browser or spider. The server must be located using a URL or URI. This always contains http:// at the start. It normally connects to port 80 on a computer.
- <ref>https://computersciencewiki.org/index.php?title=HTTP_or_HTTP/2&action=edit</ref>
- </nowiki>
-== How does it work or a deeper look ==
+== Difference between HTTP and HTTPS
-* If you are discussing a THING YOU CAN TOUCH, you must explain how it works, and the parts it is made of. Google around for an "exploded technical diagram" of your thing, [http://cdiok.com/wp-content/uploads/2012/01/MRI-Technology.jpg maybe like this example of an MRI]  It is likely you will reference outside links. Please attribute your work.
+A more secure version of HTTP is called HTTPS (Hypertext Transfer Protocol Secure). This contains https:// at the beginning of the URL. It encrypts all the information that is sent and received. This can stop malicious users such as hackers from stealing the information and is often used on payment websites. HTTPS uses port 443 for communication instead of port 80<ref>https://computersciencewiki.org/index.php?title=HTTP_or_HTTP/2&action=edit</ref>
-* If you are discussing a PROCESS OR ABSTRACT CONCEPT (like [[fuzzy logic]]) you must deeply explain how it works.
 -------------------------
-HTTP works by using a user agent to connect to a server. The user agent could be a web browser or spider. The server must be located using a URL or URI. This always contains http:// at the start. It normally connects to port 80 on a computer.
+== Request message ==
-A more secure version of HTTP is called HTTPS (Hypertext Transfer Protocol Secure). This contains https:// at the beginning of the URL. It encrypts all the information that is sent and received. This can stop malicious users such as hackers from stealing the information and is often used on payment websites. HTTPS uses port 443 for communication instead of port 80<ref>https://computersciencewiki.org/index.php?title=HTTP_or_HTTP/2&action=edit</ref>
+he request message contains the following:
--------------------------
+* Request line, such as <nowiki>GET /images/logo.gif HTTP/1.1</nowiki>, which requests the file <nowiki>logo.gif</nowiki> from the <nowiki>/images</nowiki> directory
+* Headers, such as Accept-Language: en
+* An empty line
+* An optional message body
-== Examples ==
+The request line and headers must all end with two characters: a carriage return followed by a line feed, often written <CR><LF>. The empty line must consist of only <CR><LF> and no other whitespace. In the HTTP/1.1 protocol, all headers except Host are optional.
-Please include some example of how your concept is actually used. Your example must include WHERE it is used, and WHAT IS BENEFIT of it being used.
+A request line containing only the path name is accepted by servers to maintain compatibility with HTTP clients before the HTTP/1.0 standard.
 == Pictures, diagrams ==