WordPress born as blog platform for easy of use and many other features is becoming a CMS. However, it is possible that the site is only used internally at the enterprise level, not exposed to the Internet, this could be a problem for businesses that use a Proxy for browsing. In fact WordPress often requires “go to out” our LAN, example checking for plugin/core updates, or remove the options for your blogroll. From version 2.8 programmers have added a new use of the site behind a proxy.

A few parameters (manually entered) to config.php file is required
First we define our proxy and its port:

define ('WP_PROXY_HOST', '192 .168.1.1 ');
define ('WP_PROXY_PORT', '8080 ');

If the proxy requires authentication will also add:

define ('WP_PROXY_USERNAME', 'myuser');
define ('WP_PROXY_PASSWORD', 'mypassword');

Then if we needed the proxy is not used locally or at such other intranet sites, we will proceed with these parameters:

Define ('WP_PROXY_BYPASS_HOSTS', 'localhost, other.intranet');

Finally we can block all requests to sites that are potentially unsure, so you can compile a white list for those that we believe reliable:

define ('WP_HTTP_BLOCK_EXTERNAL', 'true');
define ('WP_ACCESSIBLE_HOSTS', 'api.wordpress.org, akismet.com');