On 3/19/2020 3:48 PM, Stormy wrote:
I have, on Apache 2.4.7: https://mysite.com/ which runs a Perl/Mysql based application perfectlyand a parallel "staff only" accessed (now) only on our LAN to edit the above public application.I need to add "outside" access for staff working from home, so that I would end up with e.g.https://mysite.com/ ; [working exactly as before] and https://mysite.com/foo ; [for the "staff_only", fully working on LAN]I have tried variations of: Redirect permanent "/foo/" "http://mysite.com/staff_only/"; -- but end up with 404 every time.Is there an elegant solution for this? Many thanks -- Paul
You need to explain in more detail what you are trying to do.Is mysite.com referencing the same server whether accessed publicly or privately? Are you trying to use split-DNS to reference public vs private servers so you can use the same domain name to access a private server across a VPN?
If staff-only is confidential and on the same server as public mysite.com you still have some significant risks which can be mitigated with apache access controls (.htaccess for example)... but still not a very good idea.
If none of above is relevant to what you want to do then your redirect is to an http resource where you reference https everywhere else... is that your problem?
If still none of my discussion is relevant then what is the purpose of https://mysite.com/foo redirecting to staff_only... why not just use a URL directly to staff_only?
If working from home is completely new to your company (and I imagine there's a lot of that with current health concerns) and security is a concern then opening up private resources on a public server is not a good idea and you should look into some secure remote access solutions to access private servers across a vpn.
Jim Albert --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|