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
F14046534: D15705.id37847.diff
Wed, Nov 13, 9:44 PM
F14046420: D15705.id37847.diff
Wed, Nov 13, 9:06 PM
F14029024: D15705.id37847.diff
Fri, Nov 8, 6:53 PM
F14020063: D15705.id37835.diff
Tue, Nov 5, 11:55 PM
F14011100: D15705.id.diff
Thu, Oct 31, 5:46 PM
F13985221: D15705.id37847.diff
Sun, Oct 20, 6:57 PM
Unknown Object (File)
Oct 10 2024, 2:58 AM
Unknown Object (File)
Sep 11 2024, 9:43 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
Lint
Lint Not Applicable
Unit
Tests Not Applicable