epriestley d4bf2a147b Make paths and Aphlict instance names less ambiguous ... 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. Reviewers: chad Reviewed By: chad Maniphest Tasks: T10697, T10783 Differential Revision: https://secure.phabricator.com/D15705		2016-04-14 04:57:21 -07:00
..
AphlictAdminServer.js	Complete modernization of Aphlict configuration	2016-04-14 04:57:00 -07:00
AphlictClientServer.js	Make paths and Aphlict instance names less ambiguous	2016-04-14 04:57:21 -07:00
AphlictListener.js	Complete modernization of Aphlict configuration	2016-04-14 04:57:00 -07:00
AphlictListenerList.js	Namespace Aphlict clients by request path, plus other fixes	2015-02-16 11:31:15 -08:00
AphlictLog.js	Enable "strict" mode for NodeJS	2015-01-20 07:43:10 +11:00
javelin.js	Make the Aphlict server more resilient.	2014-06-11 10:17:12 -07:00