Page MenuHomeDevCentral

Allow to get server URL, port, name, scheme
ClosedPublic

Authored by dereckson on Apr 30 2018, 22:32.
Tags
None
Referenced Files
F2826536: D1636.id4177.diff
Thu, Apr 18, 20:26
Unknown Object (File)
Mon, Apr 15, 02:28
Unknown Object (File)
Mon, Apr 15, 02:28
Unknown Object (File)
Sat, Apr 13, 19:15
Unknown Object (File)
Wed, Apr 10, 09:41
Unknown Object (File)
Wed, Apr 10, 09:41
Unknown Object (File)
Wed, Apr 10, 08:36
Unknown Object (File)
Wed, Apr 10, 08:35
Subscribers
None

Details

Summary

To determine the URL of a server, three components are needed:
the scheme (http? https?), the name and the port.

Generally, ports won't be the in URL, as they are the default
80 or 443 ports.

Advanced network configurations

Furthermore, in back-end/front-end topologies, To determine
if we're in HTTPS requires to examine several headers.

If there is now a standard, RFC 7239 section 4, a lot of load balancers,
caches or web servers use proprietary or former de facto headers.

Deprecation

The new Request::getServerURL method supersedes get_server_url
from Keruald/Xen sites like Azhàr or Zed.

Test Plan

Unit tests provided

Diff Detail

Repository
rKOT Keruald OmniTools
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

dereckson created this revision.
dereckson edited the summary of this revision. (Show Details)
This revision is now accepted and ready to land.Apr 30 2018, 22:35
This revision was automatically updated to reflect the committed changes.