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
F18938242: D15705.diff
Tue, Nov 11, 2:54 AM
F18821266: D15705.diff
Oct 22 2025, 9:19 PM
F18779592: D15705.id37847.diff
Oct 11 2025, 2:36 PM
F18767764: D15705.diff
Oct 8 2025, 12:13 AM
F18705278: D15705.id37835.diff
Sep 28 2025, 10:42 AM
F18463821: D15705.diff
Sep 2 2025, 2:23 AM
F18141055: D15705.id37835.diff
Aug 14 2025, 5:53 AM
F17939144: D15705.diff
Jul 31 2025, 2:52 AM
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
Lint
Lint Not Applicable
Unit
Tests Not Applicable