According to specification and semantics, the protocol and the host are combined: is https://example.comit still called the host, or is it called the URL, URI, or something else?
https://example.com
Also, (https) is called a protocol or scheme? NGINX uses the scheme , but I do not see any reference to this origin.
Actually, it's all on the wiki ... https://en.wikipedia.org/wiki/Uniform_Resource_Identifier#Relationship_between_URIs.2C_URLs.2C_and_URNs
, , URL. URI - , URL - URI, . , , , : https://www.w3.org/TR/uri-clarification/#uri-schemes
, , , - origin, RFC 6454.
+ , + + . , , https://example.com, + , , ( ) - 443, TLS - , http://example.com, 80.
http://example.com
, , , - , + , - , URL- , , https://example.com http://example.com, , , http://example.com http://example.com:8888. URL- " " , - .
http://example.com:8888
( URI STD 66, RFC 3986.)
URI (, IP-) ( )
scheme
:
//
authority
path
path-abempty
, https://example.com
/
( URI , , , URI .)
HTTP RFC 2616 , URI HTTP: URI Request-URI (. ), URI abs_path , / (.. https://example.com/).
abs_path
https://example.com/
URI, HTTP , scheme authority.
IMHO, the origin is not the right term, because the origin refers to "where the message comes from." But it can also be a destination. Therefore, I believe that the base URL is the most suitable term for the protocol + host + port. See for example https://www.techopedia.com/definition/4858/base-url .