|
|
|
@ -25,13 +25,13 @@ The features you will miss out on for these files are features listed
|
|
|
|
|
|
|
|
|
|
# Supported gophermap item types
|
|
|
|
|
|
|
|
|
|
All of the following item types are supported by Gophor, separated into
|
|
|
|
|
All of the following item types are supported by Gophi, separated into
|
|
|
|
|
grouped standards. Most handling of item types is performed by the clients
|
|
|
|
|
connecting to Gophor, but when performing directory listings Gophor will
|
|
|
|
|
connecting to Gophi, but when performing directory listings Gophi will
|
|
|
|
|
attempt to automatically classify files according to the below types.
|
|
|
|
|
|
|
|
|
|
Item types listed as `[SERVER ONLY]` means that these are item types
|
|
|
|
|
recognised ONLY by Gophor and to be used when crafting a gophermap. They
|
|
|
|
|
recognised ONLY by Gophi and to be used when crafting a gophermap. They
|
|
|
|
|
provide additional methods of formatting / functionality within a gophermap,
|
|
|
|
|
and the output of these item types is usually converted to informational
|
|
|
|
|
text lines before sending to connecting clients.
|
|
|
|
@ -111,7 +111,7 @@ Errors are sent according to GopherII standards, terminating with a last
|
|
|
|
|
line:
|
|
|
|
|
`3<error text>CR-LF`
|
|
|
|
|
|
|
|
|
|
Possible Gophor errors:
|
|
|
|
|
Possible Gophi errors:
|
|
|
|
|
```
|
|
|
|
|
Text | Meaning
|
|
|
|
|
400 Bad Request | Request not understood by server due to malformed
|
|
|
|
@ -134,7 +134,7 @@ Possible Gophor errors:
|
|
|
|
|
|
|
|
|
|
## Terminating full stop
|
|
|
|
|
|
|
|
|
|
Gophor will send a terminating full-stop for menus, but not for served
|
|
|
|
|
Gophi will send a terminating full-stop for menus, but not for served
|
|
|
|
|
or executed files.
|
|
|
|
|
|
|
|
|
|
## Placeholder (null) text
|
|
|
|
|