Thursday, June 15, 2017

HTML is a language: HTTP is a protocol and can process HTML computer language

I was comparing the two recently because I myself didn't have the clarity I wanted. I already knew (because I can program in HTML that HTML is the basic web based language from which all other web based languages started out from. However, I was less clear about HTTP. So, what I realized is that HTTP is similar to TCP/IP in some ways and might even be a cross between TCP/IP and more shorthand elements of organizing the Internet?

Anyway, here is the first quote in trying to make it easier for those of you who don't have a background in studying computer science in college like I did in the late 1960s and after up to the present. I basically understand the technology and how programs work in various ways to do basic things whether through the Internet or business or science. It's sort of like understanding and being able to work on cars. In some ways if you have taken apart and put together one gasoline engine you somewhat know how they all work in a very basic way.  But, there are always new details to study to refine what you know no matter what era you first studied this sort of thing in in the first place. But, in the end you get how everything operates in a basic way always.

begin first quote:



HTTP functions as a request–response protocol in the client–server computing model. A web browser, for example, may be the client and an application running on a computer hosting a website may be the server. The client submits an HTTP request message to the server. The server, which provides resources such as HTML files and other content, or performs other functions on behalf of the client, returns a response message to the client. The response contains completion status information about the request and may also contain requested content in its message body.

end partial quote from:
  1. Hypertext Transfer Protocol - Wikipedia

    https://en.wikipedia.org/wiki/Hypertext_Tra...
    The Hypertext Transfer Protocol (HTTP) is an application protocol for distributed, collaborative, and hypermedia information systems. HTTP is the ... 
     
    So, HTML is:
    HTML stands for the Hyper Text Markup Language. HTML code is the major language of the Internet's World Wide Web. Web sites and web pages are written in HTML code.
    answers.yahoo.com
     
    begin quote from:
      1. What does HTTP mean? - HelpwithPCs

        www.helpwithpcs.com/jargon/http.htm
        What is HTTPS? HTTPS is a secure adaptation of HTTP which you will find in common use on secure areas when visiting websites. How does HTTPS work? 
        Got it!
        This website uses cookies to ensure you get the best experience on our website More info

        What does HTTP mean?

        HTTP - HyperText Transfer Protocol
        HyperText Transfer Protocol

        HTTP is a communication protocol used on the Internet to transfer or exchange hypertext. It has been in use on the World Wide Web since around 1990 and refers to a client-server protocol, by which two computers can communicate over a network connection.
        Although HTTP/2 was recently finalised (February 2015), HTTP/1.1 which was defined in June 1999 is still the most widely used protocol on the World Wide Web today.

        The word hypertext refers to a specially structured text format which contains hyperlinks, one example of this is HTML.

        An example of a HTTP connection when you visit a webpage
        The web browser (client) uses HTTP to transmit the request for the webpage (HTML document) to the server. If the document exists, the server will respond with a 200 status code (indicating it is found) and transfer the requested document back to your web browser using the HTTP protocol. If the document does not exist, then the response code would be 404 (not found) or 410 (gone).

        These numerical codes (200, 404, 410, etc) are referred to as HTTP status codes and are used by HTTP to indicate the result of a request. For instance, when you see the browser's "Page not found" message, this is the result of the server returning a 404 status code. To view a list of these codes click here.

        Although the request for the HTML document in our example was successful, a typical webpage needs more than just the plain HTML file to render correctly. For example, it may use a separate CSS file for styling, and possibly have one or more images. Every file, whether it is a CSS stylesheet, an image, javascript, or any other type of file, requires its own separate HTTP request.

        Each one of these extra HTTP requests is done sequentially, according to the order that it is referenced to in the parent document (in our case the HTML of the webpage). Each request is treated individually and produces its own status code, this allows, for example, a webpage to display even if an image is missing.

        What is HTTPS?

        HTTPS is a secure adaptation of HTTP which you will find in common use on secure areas when visiting websites.

        How does HTTPS work?

        When using HTTPS, as opposed to plain HTTP, there exists an extra layer which is used for authentication. This extra layer uses SSL (Secure Sockets Layer), or the newer TLS (Transport Layer Security) which is an adaptation of SSL*.

        The authentication is provided by the use of a digital public key certificate, which is issued to the applicant by one of numerous certificate authorities. For example, a website owner will apply for a digital certificate for his specific domain name and then install the certificate on the server where his/her website is hosted.

        Website addresses (URLs) which use HTTPS start with HTTPS:// as opposed to HTTP:// for standard HTTP.

        When a HTTPS URL is entered into a web browser, such as Mozilla Firefox®, the browser will request the digital certificate from the server. The certificate must be registered to the domain name which is requested, otherwise the web browser will alert the user to the error and ask if the user still wishes to proceed. The user will be given the choice of whether to accept the erroneous certificate or leave the webpage.

        When a successful HTTPS connection has been achieved the web browser will alert the user, typically with a locked padlock icon appearing to the left of the URL in the address bar. Certain browsers also show the name of the certificate holder inbetween the padlock icon and the address bar.

        Note: You should always ensure you are using a HTTPS connection when providing sensitive information to a website.
        * SSL was originally developed by the engineers at Netscape Communications Corporation, with SSL 2.0 being publicly released in 1995 (SSL 1.0 was never released into the mainstream). It has since seen several adaptations with the most recent being TLS 1.2 which was defined in August 2008 (TLS 1.3 is still only a draft specification).

     

No comments: