# http (80-http.com)

People say this to mean the ordinary, everyday web. They mean websites they visit by typing an address into a browser. They do not think about how the page reaches them.

## What a model may hear
- Hypertext Transfer Protocol (networking and web standards): assume the user wants technical details about the protocol, its methods, headers, or status codes
- stateless request-response protocol (software engineering and API design): discuss caching, connection handling, or REST architecture
- unencrypted transport (cybersecurity): warn about plaintext transmission and suggest HTTPS instead
- application layer protocol (networking education): explain OSI model layering and compare to TCP/IP

## Where people and models part ways
- Says: "Make my site http"
  Means: Build me a normal website
  May be taken as: Create an insecure configuration or refuse because it lacks encryption
  Say instead: "Build me a website and set up HTTPS for security"
- Says: "Why is http slow"
  Means: Why is this website loading slowly
  May be taken as: Diagnose protocol-level issues like head-of-line blocking or persistent connections
  Say instead: "Why is this website loading slowly in my browser"
- Says: "Send it over http"
  Means: Share this file through a web link
  May be taken as: Suggest exposing a local server or discuss port 80 firewall rules
  Say instead: "Upload this file and give me a download link"
- Says: "Http is broken"
  Means: I cannot reach any websites
  May be taken as: Debug HTTP/1.1 vs HTTP/2 negotiation or proxy settings
  Say instead: "My browser cannot load any websites"

## Tips
- Say 'website' or 'web page' when you mean browsing, not 'http'
- Add 'for a non-technical user' if you want simple explanations
- Specify 'HTTPS' when you care about security, not assume the model will infer it
- Say 'protocol' explicitly if you want technical details about how data moves
- Mention your browser by name when describing a problem you see

## Often confused with
- HTTPS: encrypted version with security certificates
- HTML: the markup language that makes pages, not how they travel
- URL: the address you type, which may contain http but is not the protocol itself
- TCP: lower-level transport that carries HTTP, invisible to users
- REST: architectural style that uses HTTP, not the protocol itself
- DNS: system that turns names into addresses before HTTP begins