Require ip 192.93.8.0/24 Using a Firewall The following may be a little easier to maintain than the as the campus network expands and evolves than the version above, but this version will simply give the off-campus user a standard 403 Access Denied error message without any further explanation. Alternate Method with Basic Apache HTTPD Configuration An alternate method (shown below) will just give users a 403 Forbidden error, which might be good enough in many cases. The method above will direct all outside users to /message.html on your site, where you can post a message about the site being for on-campus use only. Using 303 ensures that they'll actually get to your site once they've logged into the VPN. If you use 301 instead, then a user who connects from off-campus and gets your message file will continue to get it even if they then connect to the VPN. Also note the 303 redirect status on the last line: this tells the browser to check back with the server and not cache the redirect. The last RewriteCond line is needed to whitelist your message to off-campus users - otherwise they'll end up in an infinite redirect loop. The first three lines cover the main Atlanta campus, while the fourth line (192.93.8.) covers GT Lorraine in France, and the last 3 private campus IP space. ![]() htaccess file in the root directory of your site (on OIT Web Hosting, this goes under httpdocs or httpsdocs usually): RewriteEngine On ![]() This is a great idea for internal-use-only sites and also for all of your development/test websites if you are not using a local stack. You can restrict your site so that only people who are on-campus (or using the VPN) can access it.
0 Comments
Leave a Reply. |