T8wn

HTTP

8TML > Reference > Addresses and HTTP

Requests

Clients send HTTP/1.0 requests, GET and POST for forms, with a Host: header.

GET /games/index.8tml HTTP/1.0
Host: example.com

Responses

Status The client
2xx shows the page
301 302 303 307 follows the Location, at most 5 times in a row; after a 303 the next request is a GET
anything else tells the reader; if the body is an 8TML page, shows it too

Redirects are followed whatever their content type.

Content types

Clients never look at the file name in the address; the Content-Type header decides:

  • text/html, and any type starting with image/, audio/, video/ or font/ (compared without case, parameters ignored), isn’t loaded. The client reports an unsupported type and stays on the current page.
  • Any other type, or none, is read and shown as an 8TML page or as plain text (see Page header).

Servers should send 8TML pages as text/8tml. Clients also accept the defaults servers use for unknown files, such as application/octet-stream and text/plain. See Hosting 8TML pages.

HTTPS

https:// addresses go through the HTTPS proxy when one is configured; without one they can’t be loaded.

Contents