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)
Sat, Jul 2, 6:05 PM
Unknown Object (File)
Sat, Jun 25, 11:49 AM
Unknown Object (File)
Thu, Jun 16, 10:46 AM
Unknown Object (File)
Sun, Jun 12, 6:37 AM
Unknown Object (File)
May 29 2022, 8:54 PM
Unknown Object (File)
Apr 14 2017, 7:59 PM
Unknown Object (File)
Mar 20 2017, 2:04 PM
Unknown Object (File)
Feb 9 2017, 3:21 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