Have Geek Brain

Block web app only works for intranet

a week down the road, I will have a task to create a php web app that will run as a billing process. Once the client and my team agree, the web app will only deploy to their backend server. For this, some fundamental questions have arisen.

  • How do we block the web application will really only work on the internal server and not on the internet as he requested? the reason for this need, labor costs have been reduced to some extent. so it is best if it only works as a client describe it: it will be deployed on intranet only inside the network
  • What is pro and cons for deploying php application (with all its apache server) on intranet?
  • What is the fundamental difference between deploying a php application on an intranet and on the Internet? is there anything to consider?
  • I know we can put windows on a flash drive or pen drive. I have an apache / php autorun server that works the same?
+2


a source to share


3 answers


Set up your apache config so that only the internal network has access to the billing system using mod_authz_host.

<Directory /billing-system/docroot>
Order Deny,Allow
Deny from all
Allow from *internal ip range*
</Directory>


See http://httpd.apache.org/docs/2.1/mod/mod_authz_host.html#allow for details .

+3


a source


Just deploy a WAMP (or LAMP) server with your application on a server inside a company firewall on your network.

Users then access your application via the server name. for example, if the machine name is "Elmo", users simply access your application:

http://elmo/index.php


(assuming the server defaults to port on port 80)

The trick here is that if this computer is not connected to the internet and you need to update it externally, you will need to have other access, for example. SFTP

+1


a source


  • If the intranet is not connected to the internet, you can check this by checking a well-known site like your domain or google.com and refuse to work if it responds. But such intranets are becoming rare. It might be easier to limit the maximum number of users (total or concurrent) - it is difficult to verify that the application is not accessible from the outside.

  • Fewer attempts to hack an application (behind a company firewall) is a pro and a console, because then you might be tempted to pay less attention to security considerations because "well, this is an internal application!"

  • There is no fundamental difference. Large organizations usually have some form of SSO and you will have to integrate that; also server configuration and software may be IT limited.

  • XAMPP can be run from a manual drive, so if you can boot Windows and instruct it to run XAMPP it should be possible.

+1


a source






More articles:


All Articles