URL suffixes

How to read the tables

Each row names a suffix, the exact URL form, what it returns, who may use it and which layer answers it. A platform suffix is answered before RTEdge.net reads your deployment, on every URL of every host the platform serves. A router suffix is answered by the RTEdge.net router for a deployed route, once the router has picked the route from the URL.

Rows marked Experimental work today, but they are not part of the stable surface and may change.

Source, versions and indexes

Worker

Sign in

Usage and diagnostics

Utilities

Query parameters

These parameters change what a deployed root page returns, or filter an index. Query parameters describes each one.

Platform files

The platform answers a few fixed paths before any deployment is consulted, so a deployment cannot serve its own. Reserved paths lists them.

Notes

Reserved text in paths

The platform matches some text anywhere in a path, so these sequences are reserved, worker paths included:

• any path containing ::s goes to the sign-in handler;
• any path containing ::i, ::e, ::c, ::u, ::t or ::v, and not ending in ::clear, goes to the source, versions and usage shortcuts, which answer with an empty 404 unless the path ends in a recognized suffix;
• any path containing /::edge returns the diagnostics;
• any path ending in ::clear or ::qr is answered by that suffix.

Keep these sequences out of route, file and worker paths. /::source signs the visitor out and /::stuff returns the signed-in user, because the sign-in handler reads the letters after ::s. /a::cool redirects to /a?. A ::name that nothing claims is an ordinary worker path: /::zz reaches the worker as /:zz.

Addressing a route

Write a suffix as <route path>/::suffix. The router picks the route from the text before the first : and drops the last path segment unless that text ends in /. /docs/::meta, /docs/::kv, /docs/::owner and /docs/:api address the route name/docs. /docs::meta addresses the root route name.

The shortcuts ::u, ::t, ::i, ::e, ::c and ::v keep the whole path instead, so /docs::u and /docs::v address name/docs. Always write the slash.

Redirects to the slash form

The platform redirects some URLs before a suffix is read. A bare ? must follow a slash, so write /docs/?.

Where suffixes work

Platform suffixes answer on every URL of every host the platform serves: *.rt.ht hosts and custom domains, deployed or not. https://rtcode.io/::qr returns a QR code too. Router suffixes work on deployed routes. The in.rt.ht gateway serves any route through one origin, so https://in.rt.ht/new/::u works like https://new.rt.ht/::u.

In the playground

The playground output emulates ::su and the /: worker paths. Every other suffix on this page works on deployed URLs only. ?, ??, *, ::kv, ::meta, ::owner and the social-preview parameters are features of the RTEdge.net router. See Playground and edge differences.

See also

• Query parameters
• Reserved paths
• Request routing
• Response headers
• Error pages
• Security and access model
• Utilities