15383280
Description
Flashcards by Cosmo Brown, updated more than 1 year ago
|
Created by Cosmo Brown
about 7 years ago
|
|
| Question | Answer |
| What is a user agent? | An application acting on behalf of the user. Generally, but not limited to, a browser. |
| User agent, aka: | Client Agent |
| TCP - Definition - In layman terms | - Transfer Control Protocol - One of the main protocols on the web. If you're connecting to a service on the web, you're likely using a TCP connection. |
| IP - Definition - Layman's | - Internet Protocol - Protocol used to actually transfer data over the web |
| URL - Definition - Layman | - Uniform Resource Locator - An address pointing at a resource on the web. |
| DNS - Definition - Layman | - Domain Name Server - Points to the IP address of the server |
| Server - What they run (2) | Data Storage + Sharing Application (most commonly a web server application) |
| Proxy | Software or Hardware, acting as a middleman between clients and servers |
| Request response pairs | A request is sent, a response is returned |
| HTTP Headers | Used in the request/response pair relationship to pass information back and forth. Every request and response has one. |
| HTTP Request Method/Verb | Every HTTP request contains a method explaining the action the sender wants to perform on the resource |
| Status Response Code | Numerical Code in the 100-500 range describing what type of response the server sent back to the client |
| Cache | Method of storing data on the client or server to speed up performance |
| Stateless, in terms of HTTP | There is no link between two requests sent between the client and the server |
| Cookies | A string of data passed between the client and the server to create a state-full connection. |
| Session | Clients/Servers pass info on their current state back and forth to each other, creating a session. |
| Nameservers | Direct to the domain name to the IP address |
| Top Level Domain (TLD) | - Provide info about the general purpose of the site - .com, .org, .gov etc. |
| Secondary Level Domain | Label right before '.com' |
| Subdomain | - Part of the larger domain, generally used to create a subsection of the website - ex: subdomain.mysite.com |
| Registrar | Organization that manages the reservation of domain names |
| Country Codes - Layman - Where in url | - Each country has a 2 letter code to represent them - Some act as TLDs, sometimes as a SLDs |
| URL: Protocol Declaration | - Declares HOW we are accessing the resource |
| URL: URN | - Universal Resource Name - Provides the location of the resource |
| URL: Host | - aka Domain |
| URL: Resource Path | - The location of the file within the server |
| URL: Host - Location | ex: mysite.com |
| URL: URN - Location | After the protocol ( after 'https://' ) |
| URL : Resource Path - Location | After '.com' ex: mysite.com/info/jim-info/hello.htm |
| URL - URL Query | - One or more queries that can perform further actions on the server (optional) - Start with a '?', then each is comprised of an argument and a value. - If +1, '&' strings them together ex: ?u=1234 ex2: ?a=111&b=222 |
| URL: URL Query - Location | - After the resource path site.com/about/me.htm?u=456&b=222 |
| HTTP Method: GET | - Get the specified resource, if available - Only needs the method and the URL to work (though an authorization header is possible) |
| HTTP Method: POST | - Create a new resource and add it to a collection in the server - Typically needs an authorization header |
| HTTP Methods: PUT | - Update an existing resource (in the server) - Typically needs authorization header |
| HTTP Methods: PUT - If no resource | If the resource that PUT is trying to change does not exist, the server may allow that resource to be created, or may send an error message. Depends on the server. |
| HTTP Methods: PATCH | - Modify an existing resource - Unlike PUT, which replaces content, PATCH can modify content without necessarily replacing it - Typically requires auth |
| HTTP Methods: DELETE | - Deletes a resource |
| HTTP Methods: DELETE - Server action | Depending on how the server is configured, a delete request may... : - Delete a database entry - Change the status of a database entry without actually removing content |
| HTTP Methods: HEAD | - Returns just the head section of the response |
| HTTP Status Code - 1xx | Information - Rarely encoutnered |
| HTTP Status Code - 2xx | Success |
| HTTP Status Code - 3xx | Redirection |
| HTTP Status Code - 4xx | Client Error |
| HTTP Status Code - 5xx | Server Error |
Want to create your own Flashcards for free with GoConqr? Learn more.