If my customer is example.com, with multiple applications and services
routed to that domain e.g. /blog or login.example.com. One service that
they are hosting is a MediaWiki instance at https://example.com*/wiki*
(also using a single-sign-on infrastructure - but I don't think that
matters much for this discussion about SSL and routing requests for
top-level folders of the domain). For them to outsource the wiki hosting,
and continue to have the wiki hosted at /wiki using an SSL certificate that
they provide, what needs to be done?
I'm assuming that if I have a static IP address xx.xx.xx.xx, and an SSL
certificate for "wiki.example.com", that the customer can use DNS to make
sure that wiki.example.com points to that IP. The customer can use their
web-server to internally proxy requests for /wiki to wiki.example.com/wiki
and to the end-user they would simply see https://example.com/wiki in their
browser (preserving existing links and SEO built up at that path). Is this
correct?
And, what ways can latency and overhead be reduced so that their server can
hand-off requests as efficiently as possible under a high load environment?
Thanks,
Greg
Greg Rundlett
*principal consultant*
eQuality Technology
*Let's work together*
https://equality-tech.com
follow us: https://twitter.com/eQualityTech
like us: https://www.facebook.com/eQualityTechnology/
*Get a free wiki report*: https://freephile.org/wikireport/
Heya,
I’m a member of the MediaWiki stakeholders group and we just hosted
the third Enterprise MediaWiki conference. I’d like to start using
this list more to help the community with communication. Would it be
possible to help administer this list?
Yours,
Chris K.