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
Unknown Object (File)
Fri, Jun 26, 8:11 AM
Unknown Object (File)
Sun, Jun 21, 1:58 AM
Unknown Object (File)
Apr 1 2026, 11:47 PM
Unknown Object (File)
Mar 29 2026, 12:24 PM
Unknown Object (File)
Mar 5 2026, 9:57 AM
Unknown Object (File)
Feb 9 2026, 12:55 AM
Unknown Object (File)
Jan 28 2026, 11:48 PM
Unknown Object (File)
Jan 19 2026, 1:19 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
Branch
aphlict6
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 11703
Build 14658: Run Core Tests
Build 14657: arc lint + arc unit