Page MenuHomePhabricator

Make paths and Aphlict instance names less ambiguous
ClosedPublic

Authored by epriestley on Apr 13 2016, 11:11 PM.
Tags
None
Referenced Files
F18141055: D15705.id37835.diff
Thu, Aug 14, 5:53 AM
F17939144: D15705.diff
Jul 31 2025, 2:52 AM
F17790955: D15705.id37835.diff
Jul 24 2025, 9:06 PM
F17756535: D15705.diff
Jul 22 2025, 2:19 PM
Unknown Object (File)
May 27 2025, 11:02 AM
Unknown Object (File)
May 9 2025, 6:33 PM
Unknown Object (File)
May 8 2025, 7:52 PM
Unknown Object (File)
Apr 13 2025, 6:14 PM
Subscribers
None
Tokens
"Like" token, awarded by salvian.

Details

Summary

Fixes T10783 (what little of it remains). Ref T10697.

Aphlict currently uses request paths for two different things:

  • multi-tenant instancing in the Phacility cluster (each instance gets its own namespace within an Aphlict server);
  • some users configure nginx and apache to do proxying or SSL termination based on the path.

Currently, these can collide.

Put a "~" before the instance name to make it unambiguous. At some point we can possibly just use a GET parameter, but I think there was some reason I didn't do that originally and this sequence of changes is disruptive enough already.

Test Plan

Saw local Aphlict unambiguously recognize "local.phacility.com" as instance "local", with a "~"-style URI.

Diff Detail

Repository
rP Phabricator
Branch
aphlict6
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 11703
Build 14658: Run Core Tests
Build 14657: arc lint + arc unit