Post History

[RFC 3986](https://www.rfc-editor.org/rfc/rfc3986#section-4.5) defines a *suffix reference* as follows (emphasis my own):

>### 4.5.  Suffix Reference
>The URI syntax is designed for unambiguous reference to resources and extensibility via the URI scheme.  However, as URI identification and usage have become commonplace, traditional media (television, radio, newspapers, billboards, etc.) have increasingly used a suffix of the URI as a reference, **consisting of only the authority and path portions of the URI**, such as
>
>      www.w3.org/Addressing/
>
>or simply a DNS registered name on its own.  Such references are primarily intended for human interpretation rather than for machines,
with the assumption that context-based heuristics are sufficient to complete the URI (e.g., most registered names beginning with "www" are likely to have a URI prefix of "http://").  Although there is no standard set of heuristics for disambiguating a URI suffix, many client implementations allow them to be entered by the user and heuristically resolved.

This is not quite what you've literally asked for, as the authority also optionally includes "userinfo" and the port[^1], but it's as close as I could find to a standardized term and it mentions that this is what many implementations will accept when resolving URIs. If you really want to be specific, it's probably easiest just to say "host + path".

[^1]:```
     authority   = [ userinfo "@" ] host [ ":" port ]
     ```