_at_Ajay - VPN would be my last resort if nothing really works. so i'll try to
see which options are available before switching to a VPN :D
_at_Nadim - This is not a bad idea. I should give it a try and also see if
there are any security issues.
Thanks :D
On Fri, May 1, 2015 at 12:11 AM, Mohammad Nadim <nadim.attari_at_gmail.com>
wrote:
> Hello Yuv,
>
>
>
>
> On 30 April 2015 at 20:18, Yuv Joodhisty <locustv2_at_gmail.com> wrote:
>
>> Hello guys,
>>
>> Does anyone have any idea how to tackle this problem?
>> I need a virtual host which should be:
>>
>> - accessible locally but not publicly
>> - may be accessible by some remote users
>> - those remote users doesn't have a static ip
>>
>>
>
> I'm no sysadmin, so they'll answer you better.
>
> BTW, see this link:
>
> https://www.linode.com/docs/websites/apache-tips-and-tricks/rulebased-access-control-for-apache
>
> Dunno if it's possible, but give a try. Configure Apache to
>
> - Allow all from intranet
> - If not from intranet, then check whether some parameter is set in
> HTTP header sent by browser to the server
> - If yes, allow access
> - Else redirect to a page displaying "You are not allowed to access
> this resource, etc"
>
> Since you have **some** remote users, you can ask them to install a
> plugin on their browsers (say Firefox) that automatically modifies the HTTP
> header that is sent to the server (the plugin adds the parameter Apache is
> going to check). Up to you to develop this Firefox plugin and distribute to
> your **some** remote users :-)
>
> Else use a VPN.
>
> Hope it helps.
>
> Best regards,
> Nadim Attari
>
> p.s.: Modify this plugin to develop yours.
> https://github.com/garethhunt/modifyheaders
>
Received on Fri May 01 2015 - 11:59:41 PST