# http (1-http.org)

HTTP is how a browser asks a website for a page and gets it back. People say it as letters or sometimes as a word, 'h-t-t-p,' when they mean the start of a web address.

## What a model may hear
- application protocol (networking and web standards): treat the word as a specific protocol with methods (GET, POST), headers, status codes, and version history
- insecure transport flag (security and browser policy): flag the connection as unencrypted, warn the user, or refuse to load mixed content
- URI scheme (URL parsing and routing): use it to choose a handler, set default port 80, and strip or normalize the scheme
- legacy fallback (redirect and upgrade logic): automatically rewrite to HTTPS or block the request entirely

## Where people and models part ways
- Says: "Go to http"
  Means: Open this website in my browser
  May be taken as: Assume the user wants raw protocol details, curl-like output, or a debugging session
  Say instead: "Open this website in my browser: http://example.com"
- Says: "Fix the http"
  Means: The link is broken or the page won't load
  May be taken as: Diagnose HTTP headers, status codes, or server configuration instead of checking the URL for typos
  Say instead: "This page won't load. Can you check if the URL is wrong or the site is down?"
- Says: "What is http"
  Means: Explain how web browsing works in simple terms
  May be taken as: Deliver RFC 2616 specifications or describe packet-level behavior
  Say instead: "Explain in plain terms how a browser gets a webpage from a website"
- Says: "Use http not https"
  Means: I need the unencrypted version for a specific reason
  May be taken as: Override security settings, disable upgrades, or assume the user is testing something technical
  Say instead: "I need to access the HTTP version of this site, not the HTTPS version, because [reason]"

## Tips
- Always include the full URL with http:// so the model knows you mean a web address
- Say 'web address' or 'website' if you do not need technical protocol discussion
- Mention 'browser' to steer the model toward user-facing help, not server configuration
- Say 'unencrypted' or 'not secure' if you mean the security aspect, not the protocol itself
- Ask for 'simple explanation' or 'for a beginner' to avoid RFC-level detail

## Often confused with
- https: encrypted version with TLS
- html: the page content, not the transport
- url: the whole address, of which http is one part
- ftp: older file transfer protocol, not web pages
- tcp: lower-level transport, not the application layer
- rest: design pattern that uses HTTP, not the protocol itself