Http Basics
Download as PPTX, PDF0 likes72 views
This document provides an overview of key HTTP concepts including developer tools, security, sessions, cookies, caching, APIs, and resources for learning more. It discusses Google Chrome developer tools and their panels for debugging websites. It also covers how HTTP and HTTPS work, including how HTTPS uses encryption and SSL certificates. Additionally, it explains how cookies are used to make HTTP stateful through client-side storage of values and how they can be used for authentication, personalization, and tracking.
Http Basics
- 1. HTTP Basics (Cont.) Things You (Dev, QA) Must Know
- 2. Developer Tools ● Google Chrome Dev Tool ● Dev Tool Panels ○ Elements ○ Console ○ Sources ○ Network ○ Performance ○ Memory ○ Application ○ Security ○ Audits
- 3. Security (HTTP & HTTPS)
- 4. Security (HTTP & HTTPS) ● HTTP ○ People didn’t think everything through
- 5. Security (HTTP & HTTPS) ● HTTPS ○ Secure HTTP (TLS 1.2) ○ Uses SSL Certificates to ensure server and/or client identity ○ Uses encryption to make sure data is not interceptable
- 6. Session (Making HTTP Stateful) ● HTTP is Stateless ● Web applications are *mostly* stateful ● How to identify subsequent requests from the same client
- 7. Cookies ● Simple Key-Value client side storage ● Usage ○ Authentication/Session Tracking ○ Personalization (Locale, Theme) ○ Web Activity Tracking (Adds) ○ Server Tracking (for clustered environments) ● Create HTTP Cookie ○ Set-Cookie: <cookie-name>=<cookie-value> ■ In server response header to tell client to store the cookie ○ Cookie: <cookie-name>=<cookie-value> ■ In client request header to let server know the info
- 8. Cookies (cont.) ● Types of Cookie ○ Session vs Permanent cookies ■ Use Max-Age or Expires directive ○ Secure cookies ■ Only over HTTPS ○ HttpOnly cookies ■ Not accessible with JavaScript ■ To mitigate XSS ● Scope ○ Domain and Path ○ SameSite cookies (None, Strict, Lax)
- 9. HTTP Caching ● Fetching data from server over network is expensive ● Some resources don’t change *at least for some time* ● Re-usability ● Cache Invalidation ○ Most difficult problem in Computer Science
- 10. APIs ● Interface to communicate with the server ● RESTfulness ○ REpresentational State Transfer ○ NOT A STANDARD, it’s an Architectural Style
- 11. Emulating API Calls ● Wake Up! ● Postman ● HTTP client to make API calls ● Demo
- 12. If You Want To Outsmart Devs ● Lighthouse
- 13. Resources (for those of you who are nerds) ● Google Developer (Web) ○ https://developers.google.com/web/fundamentals ● Google Chrome Developer Tool Crash Course ○ https://youtu.be/x4q86IjJFag ● Chrome Developers YouTube Channel ○ https://www.youtube.com/user/ChromeDevelopers/
- 14. Did You Get Everything So Far?