Heads up! To view this whole video, sign in with your Courses account or enroll in your free 7-day trial. Sign In Enroll

How the Web Works

Preview

Start a free Courses trial
to watch this video

Sign up for Treehouse

HTTP and HTTPS

3:14 with Joy Kesten

Each request you make on the web is sent using the HyperText Transfer Protocol, or HTTP. HTTP is how clients and servers talk to each other on the web. HTTPs means the communication between the client and server are encrypted.

HTTP Status Codes

Related Discussions

Have questions about this video? Start a discussion with the community and Treehouse staff.

Sign up

    Related Discussions

    Have questions about this video? Start a discussion with the community and Treehouse staff.

    Sign up

    Each request you make on the web is sent using the hypertext transfer protocol or 0:00
    HTTP. 0:06
    HTTP is how clients and servers talk to each other on the web. 0:07
    Because there are so many different types of clients and servers, 0:12
    there needs to be some rules in place for 0:15
    everyone to be able to talk to each other and HTTP lays out those ground rules. 0:18
    In each HTTP exchange, two bits of information are sent back to the client. 0:22
    First, the status code and 0:28
    then the resource you requested like a web page or file. 0:30
    HTTP status codes help identify the cause of the problem when a web page or 0:33
    other resource doesn't load properly. 0:38
    The HTTP specifications define certain number ranges for 0:42
    specific types of responses. 0:47
    One you might recognize is the infamous 404 page not found. 0:50
    Here's a particularly beautiful one, but 0:55
    404 is just one of the many status codes that can be returned as an HTTP response. 0:59
    Each of the status codes are three numbers long and 1:05
    use the first number to categorize the status. 1:08
    For example, 100 responses are informational, 1:12
    200 responses means success, 300 responses mean redirection. 1:17
    400 responses mean a client error and 500 responses mean a server error. 1:24
    We'll stop there for now to give us a chance to talk about HTTPS, 1:32
    the secure version of HTTP. 1:37
    But if you're interested, 1:40
    I've put some more information about status codes in the Teacher's Notes. 1:41
    Sometimes, in your travels around the web, you'll see a lock icon in the address bar. 1:46
    The lock will usually be all the way to the left and 1:51
    the URL will start with https not http. 1:56
    The s stands for secure and it means that communication between your client and 2:00
    the server is private and encrypted. 2:06
    When surfing the web, don't use sites with sensitive information, 2:09
    like medical records banking details or 2:14
    even just username and passwords if they don't have the lock. 2:17
    Wow. 2:21
    That was a lot of information, acronyms and terminology. 2:22
    But don't think you have to memorize them all right now. 2:26
    At this point, knowing how stuff works is what's most important. 2:28
    To review, every web request starts with typing in or 2:33
    clicking something on the web. 2:36
    Often times, you find what you need using a URL, but 2:38
    URLs can also be hidden behind hyperlinks. 2:42
    Included in a URL is a domain name. 2:45
    Domain names are really just catchy versions of IP addresses and 2:48
    domain name servers make the connection between domain names and IP addresses. 2:52
    Clients ans servers are designed to talk to each other using HTTP. 2:58
    The common language they have agreed to speak, but 3:02
    none of these pieces of software have to work together so nicely. 3:05
    It's up to developers to work together and that's what makes the web work. 3:09

    You need to sign up for Treehouse in order to download course files.

    Sign up

      You need to sign up for Treehouse in order to set up Workspace

      Sign up