danielebarchiesi@0: <?php
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * @file
danielebarchiesi@0:  * Drupal site-specific configuration file.
danielebarchiesi@0:  *
danielebarchiesi@0:  * IMPORTANT NOTE:
danielebarchiesi@0:  * This file may have been set to read-only by the Drupal installation program.
danielebarchiesi@0:  * If you make changes to this file, be sure to protect it again after making
danielebarchiesi@0:  * your modifications. Failure to remove write permissions to this file is a
danielebarchiesi@0:  * security risk.
danielebarchiesi@0:  *
danielebarchiesi@0:  * The configuration file to be loaded is based upon the rules below. However
danielebarchiesi@0:  * if the multisite aliasing file named sites/sites.php is present, it will be
danielebarchiesi@0:  * loaded, and the aliases in the array $sites will override the default
danielebarchiesi@0:  * directory rules below. See sites/example.sites.php for more information about
danielebarchiesi@0:  * aliases.
danielebarchiesi@0:  *
danielebarchiesi@0:  * The configuration directory will be discovered by stripping the website's
danielebarchiesi@0:  * hostname from left to right and pathname from right to left. The first
danielebarchiesi@0:  * configuration file found will be used and any others will be ignored. If no
danielebarchiesi@0:  * other configuration file is found then the default configuration file at
danielebarchiesi@0:  * 'sites/default' will be used.
danielebarchiesi@0:  *
danielebarchiesi@0:  * For example, for a fictitious site installed at
danielebarchiesi@0:  * http://www.drupal.org:8080/mysite/test/, the 'settings.php' file is searched
danielebarchiesi@0:  * for in the following directories:
danielebarchiesi@0:  *
danielebarchiesi@0:  * - sites/8080.www.drupal.org.mysite.test
danielebarchiesi@0:  * - sites/www.drupal.org.mysite.test
danielebarchiesi@0:  * - sites/drupal.org.mysite.test
danielebarchiesi@0:  * - sites/org.mysite.test
danielebarchiesi@0:  *
danielebarchiesi@0:  * - sites/8080.www.drupal.org.mysite
danielebarchiesi@0:  * - sites/www.drupal.org.mysite
danielebarchiesi@0:  * - sites/drupal.org.mysite
danielebarchiesi@0:  * - sites/org.mysite
danielebarchiesi@0:  *
danielebarchiesi@0:  * - sites/8080.www.drupal.org
danielebarchiesi@0:  * - sites/www.drupal.org
danielebarchiesi@0:  * - sites/drupal.org
danielebarchiesi@0:  * - sites/org
danielebarchiesi@0:  *
danielebarchiesi@0:  * - sites/default
danielebarchiesi@0:  *
danielebarchiesi@0:  * Note that if you are installing on a non-standard port number, prefix the
danielebarchiesi@0:  * hostname with that number. For example,
danielebarchiesi@0:  * http://www.drupal.org:8080/mysite/test/ could be loaded from
danielebarchiesi@0:  * sites/8080.www.drupal.org.mysite.test/.
danielebarchiesi@0:  *
danielebarchiesi@0:  * @see example.sites.php
danielebarchiesi@0:  * @see conf_path()
danielebarchiesi@0:  */
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * Database settings:
danielebarchiesi@0:  *
danielebarchiesi@0:  * The $databases array specifies the database connection or
danielebarchiesi@0:  * connections that Drupal may use.  Drupal is able to connect
danielebarchiesi@0:  * to multiple databases, including multiple types of databases,
danielebarchiesi@0:  * during the same request.
danielebarchiesi@0:  *
danielebarchiesi@0:  * Each database connection is specified as an array of settings,
danielebarchiesi@0:  * similar to the following:
danielebarchiesi@0:  * @code
danielebarchiesi@0:  * array(
danielebarchiesi@0:  *   'driver' => 'mysql',
danielebarchiesi@0:  *   'database' => 'databasename',
danielebarchiesi@0:  *   'username' => 'username',
danielebarchiesi@0:  *   'password' => 'password',
danielebarchiesi@0:  *   'host' => 'localhost',
danielebarchiesi@0:  *   'port' => 3306,
danielebarchiesi@0:  *   'prefix' => 'myprefix_',
danielebarchiesi@0:  *   'collation' => 'utf8_general_ci',
danielebarchiesi@0:  * );
danielebarchiesi@0:  * @endcode
danielebarchiesi@0:  *
danielebarchiesi@0:  * The "driver" property indicates what Drupal database driver the
danielebarchiesi@0:  * connection should use.  This is usually the same as the name of the
danielebarchiesi@0:  * database type, such as mysql or sqlite, but not always.  The other
danielebarchiesi@0:  * properties will vary depending on the driver.  For SQLite, you must
danielebarchiesi@0:  * specify a database file name in a directory that is writable by the
danielebarchiesi@0:  * webserver.  For most other drivers, you must specify a
danielebarchiesi@0:  * username, password, host, and database name.
danielebarchiesi@0:  *
danielebarchiesi@0:  * Some database engines support transactions.  In order to enable
danielebarchiesi@0:  * transaction support for a given database, set the 'transactions' key
danielebarchiesi@0:  * to TRUE.  To disable it, set it to FALSE.  Note that the default value
danielebarchiesi@0:  * varies by driver.  For MySQL, the default is FALSE since MyISAM tables
danielebarchiesi@0:  * do not support transactions.
danielebarchiesi@0:  *
danielebarchiesi@0:  * For each database, you may optionally specify multiple "target" databases.
danielebarchiesi@0:  * A target database allows Drupal to try to send certain queries to a
danielebarchiesi@0:  * different database if it can but fall back to the default connection if not.
danielebarchiesi@0:  * That is useful for master/slave replication, as Drupal may try to connect
danielebarchiesi@0:  * to a slave server when appropriate and if one is not available will simply
danielebarchiesi@0:  * fall back to the single master server.
danielebarchiesi@0:  *
danielebarchiesi@0:  * The general format for the $databases array is as follows:
danielebarchiesi@0:  * @code
danielebarchiesi@0:  * $databases['default']['default'] = $info_array;
danielebarchiesi@0:  * $databases['default']['slave'][] = $info_array;
danielebarchiesi@0:  * $databases['default']['slave'][] = $info_array;
danielebarchiesi@0:  * $databases['extra']['default'] = $info_array;
danielebarchiesi@0:  * @endcode
danielebarchiesi@0:  *
danielebarchiesi@0:  * In the above example, $info_array is an array of settings described above.
danielebarchiesi@0:  * The first line sets a "default" database that has one master database
danielebarchiesi@0:  * (the second level default).  The second and third lines create an array
danielebarchiesi@0:  * of potential slave databases.  Drupal will select one at random for a given
danielebarchiesi@0:  * request as needed.  The fourth line creates a new database with a name of
danielebarchiesi@0:  * "extra".
danielebarchiesi@0:  *
danielebarchiesi@0:  * For a single database configuration, the following is sufficient:
danielebarchiesi@0:  * @code
danielebarchiesi@0:  * $databases['default']['default'] = array(
danielebarchiesi@0:  *   'driver' => 'mysql',
danielebarchiesi@0:  *   'database' => 'databasename',
danielebarchiesi@0:  *   'username' => 'username',
danielebarchiesi@0:  *   'password' => 'password',
danielebarchiesi@0:  *   'host' => 'localhost',
danielebarchiesi@0:  *   'prefix' => 'main_',
danielebarchiesi@0:  *   'collation' => 'utf8_general_ci',
danielebarchiesi@0:  * );
danielebarchiesi@0:  * @endcode
danielebarchiesi@0:  *
danielebarchiesi@0:  * You can optionally set prefixes for some or all database table names
danielebarchiesi@0:  * by using the 'prefix' setting. If a prefix is specified, the table
danielebarchiesi@0:  * name will be prepended with its value. Be sure to use valid database
danielebarchiesi@0:  * characters only, usually alphanumeric and underscore. If no prefixes
danielebarchiesi@0:  * are desired, leave it as an empty string ''.
danielebarchiesi@0:  *
danielebarchiesi@0:  * To have all database names prefixed, set 'prefix' as a string:
danielebarchiesi@0:  * @code
danielebarchiesi@0:  *   'prefix' => 'main_',
danielebarchiesi@0:  * @endcode
danielebarchiesi@0:  * To provide prefixes for specific tables, set 'prefix' as an array.
danielebarchiesi@0:  * The array's keys are the table names and the values are the prefixes.
danielebarchiesi@0:  * The 'default' element is mandatory and holds the prefix for any tables
danielebarchiesi@0:  * not specified elsewhere in the array. Example:
danielebarchiesi@0:  * @code
danielebarchiesi@0:  *   'prefix' => array(
danielebarchiesi@0:  *     'default'   => 'main_',
danielebarchiesi@0:  *     'users'     => 'shared_',
danielebarchiesi@0:  *     'sessions'  => 'shared_',
danielebarchiesi@0:  *     'role'      => 'shared_',
danielebarchiesi@0:  *     'authmap'   => 'shared_',
danielebarchiesi@0:  *   ),
danielebarchiesi@0:  * @endcode
danielebarchiesi@0:  * You can also use a reference to a schema/database as a prefix. This may be
danielebarchiesi@0:  * useful if your Drupal installation exists in a schema that is not the default
danielebarchiesi@0:  * or you want to access several databases from the same code base at the same
danielebarchiesi@0:  * time.
danielebarchiesi@0:  * Example:
danielebarchiesi@0:  * @code
danielebarchiesi@0:  *   'prefix' => array(
danielebarchiesi@0:  *     'default'   => 'main.',
danielebarchiesi@0:  *     'users'     => 'shared.',
danielebarchiesi@0:  *     'sessions'  => 'shared.',
danielebarchiesi@0:  *     'role'      => 'shared.',
danielebarchiesi@0:  *     'authmap'   => 'shared.',
danielebarchiesi@0:  *   );
danielebarchiesi@0:  * @endcode
danielebarchiesi@0:  * NOTE: MySQL and SQLite's definition of a schema is a database.
danielebarchiesi@0:  *
danielebarchiesi@0:  * Advanced users can add or override initial commands to execute when
danielebarchiesi@0:  * connecting to the database server, as well as PDO connection settings. For
danielebarchiesi@0:  * example, to enable MySQL SELECT queries to exceed the max_join_size system
danielebarchiesi@0:  * variable, and to reduce the database connection timeout to 5 seconds:
danielebarchiesi@0:  *
danielebarchiesi@0:  * @code
danielebarchiesi@0:  * $databases['default']['default'] = array(
danielebarchiesi@0:  *   'init_commands' => array(
danielebarchiesi@0:  *     'big_selects' => 'SET SQL_BIG_SELECTS=1',
danielebarchiesi@0:  *   ),
danielebarchiesi@0:  *   'pdo' => array(
danielebarchiesi@0:  *     PDO::ATTR_TIMEOUT => 5,
danielebarchiesi@0:  *   ),
danielebarchiesi@0:  * );
danielebarchiesi@0:  * @endcode
danielebarchiesi@0:  *
danielebarchiesi@0:  * WARNING: These defaults are designed for database portability. Changing them
danielebarchiesi@0:  * may cause unexpected behavior, including potential data loss.
danielebarchiesi@0:  *
danielebarchiesi@0:  * @see DatabaseConnection_mysql::__construct
danielebarchiesi@0:  * @see DatabaseConnection_pgsql::__construct
danielebarchiesi@0:  * @see DatabaseConnection_sqlite::__construct
danielebarchiesi@0:  *
danielebarchiesi@0:  * Database configuration format:
danielebarchiesi@0:  * @code
danielebarchiesi@0:  *   $databases['default']['default'] = array(
danielebarchiesi@0:  *     'driver' => 'mysql',
danielebarchiesi@0:  *     'database' => 'databasename',
danielebarchiesi@0:  *     'username' => 'username',
danielebarchiesi@0:  *     'password' => 'password',
danielebarchiesi@0:  *     'host' => 'localhost',
danielebarchiesi@0:  *     'prefix' => '',
danielebarchiesi@0:  *   );
danielebarchiesi@0:  *   $databases['default']['default'] = array(
danielebarchiesi@0:  *     'driver' => 'pgsql',
danielebarchiesi@0:  *     'database' => 'databasename',
danielebarchiesi@0:  *     'username' => 'username',
danielebarchiesi@0:  *     'password' => 'password',
danielebarchiesi@0:  *     'host' => 'localhost',
danielebarchiesi@0:  *     'prefix' => '',
danielebarchiesi@0:  *   );
danielebarchiesi@0:  *   $databases['default']['default'] = array(
danielebarchiesi@0:  *     'driver' => 'sqlite',
danielebarchiesi@0:  *     'database' => '/path/to/databasefilename',
danielebarchiesi@0:  *   );
danielebarchiesi@0:  * @endcode
danielebarchiesi@0:  */
danielebarchiesi@0: $databases = array();
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * Access control for update.php script.
danielebarchiesi@0:  *
danielebarchiesi@0:  * If you are updating your Drupal installation using the update.php script but
danielebarchiesi@0:  * are not logged in using either an account with the "Administer software
danielebarchiesi@0:  * updates" permission or the site maintenance account (the account that was
danielebarchiesi@0:  * created during installation), you will need to modify the access check
danielebarchiesi@0:  * statement below. Change the FALSE to a TRUE to disable the access check.
danielebarchiesi@0:  * After finishing the upgrade, be sure to open this file again and change the
danielebarchiesi@0:  * TRUE back to a FALSE!
danielebarchiesi@0:  */
danielebarchiesi@0: $update_free_access = FALSE;
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * Salt for one-time login links and cancel links, form tokens, etc.
danielebarchiesi@0:  *
danielebarchiesi@0:  * This variable will be set to a random value by the installer. All one-time
danielebarchiesi@0:  * login links will be invalidated if the value is changed. Note that if your
danielebarchiesi@0:  * site is deployed on a cluster of web servers, you must ensure that this
danielebarchiesi@0:  * variable has the same value on each server. If this variable is empty, a hash
danielebarchiesi@0:  * of the serialized database credentials will be used as a fallback salt.
danielebarchiesi@0:  *
danielebarchiesi@0:  * For enhanced security, you may set this variable to a value using the
danielebarchiesi@0:  * contents of a file outside your docroot that is never saved together
danielebarchiesi@0:  * with any backups of your Drupal files and database.
danielebarchiesi@0:  *
danielebarchiesi@0:  * Example:
danielebarchiesi@0:  *   $drupal_hash_salt = file_get_contents('/home/example/salt.txt');
danielebarchiesi@0:  *
danielebarchiesi@0:  */
danielebarchiesi@0: $drupal_hash_salt = '';
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * Base URL (optional).
danielebarchiesi@0:  *
danielebarchiesi@0:  * If Drupal is generating incorrect URLs on your site, which could
danielebarchiesi@0:  * be in HTML headers (links to CSS and JS files) or visible links on pages
danielebarchiesi@0:  * (such as in menus), uncomment the Base URL statement below (remove the
danielebarchiesi@0:  * leading hash sign) and fill in the absolute URL to your Drupal installation.
danielebarchiesi@0:  *
danielebarchiesi@0:  * You might also want to force users to use a given domain.
danielebarchiesi@0:  * See the .htaccess file for more information.
danielebarchiesi@0:  *
danielebarchiesi@0:  * Examples:
danielebarchiesi@0:  *   $base_url = 'http://www.example.com';
danielebarchiesi@0:  *   $base_url = 'http://www.example.com:8888';
danielebarchiesi@0:  *   $base_url = 'http://www.example.com/drupal';
danielebarchiesi@0:  *   $base_url = 'https://www.example.com:8888/drupal';
danielebarchiesi@0:  *
danielebarchiesi@0:  * It is not allowed to have a trailing slash; Drupal will add it
danielebarchiesi@0:  * for you.
danielebarchiesi@0:  */
danielebarchiesi@0: # $base_url = 'http://www.example.com';  // NO trailing slash!
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * PHP settings:
danielebarchiesi@0:  *
danielebarchiesi@0:  * To see what PHP settings are possible, including whether they can be set at
danielebarchiesi@0:  * runtime (by using ini_set()), read the PHP documentation:
danielebarchiesi@0:  * http://www.php.net/manual/en/ini.list.php
danielebarchiesi@0:  * See drupal_environment_initialize() in includes/bootstrap.inc for required
danielebarchiesi@0:  * runtime settings and the .htaccess file for non-runtime settings. Settings
danielebarchiesi@0:  * defined there should not be duplicated here so as to avoid conflict issues.
danielebarchiesi@0:  */
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * Some distributions of Linux (most notably Debian) ship their PHP
danielebarchiesi@0:  * installations with garbage collection (gc) disabled. Since Drupal depends on
danielebarchiesi@0:  * PHP's garbage collection for clearing sessions, ensure that garbage
danielebarchiesi@0:  * collection occurs by using the most common settings.
danielebarchiesi@0:  */
danielebarchiesi@0: ini_set('session.gc_probability', 1);
danielebarchiesi@0: ini_set('session.gc_divisor', 100);
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * Set session lifetime (in seconds), i.e. the time from the user's last visit
danielebarchiesi@0:  * to the active session may be deleted by the session garbage collector. When
danielebarchiesi@0:  * a session is deleted, authenticated users are logged out, and the contents
danielebarchiesi@0:  * of the user's $_SESSION variable is discarded.
danielebarchiesi@0:  */
danielebarchiesi@0: ini_set('session.gc_maxlifetime', 200000);
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * Set session cookie lifetime (in seconds), i.e. the time from the session is
danielebarchiesi@0:  * created to the cookie expires, i.e. when the browser is expected to discard
danielebarchiesi@0:  * the cookie. The value 0 means "until the browser is closed".
danielebarchiesi@0:  */
danielebarchiesi@0: ini_set('session.cookie_lifetime', 2000000);
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * If you encounter a situation where users post a large amount of text, and
danielebarchiesi@0:  * the result is stripped out upon viewing but can still be edited, Drupal's
danielebarchiesi@0:  * output filter may not have sufficient memory to process it.  If you
danielebarchiesi@0:  * experience this issue, you may wish to uncomment the following two lines
danielebarchiesi@0:  * and increase the limits of these variables.  For more information, see
danielebarchiesi@0:  * http://php.net/manual/en/pcre.configuration.php.
danielebarchiesi@0:  */
danielebarchiesi@0: # ini_set('pcre.backtrack_limit', 200000);
danielebarchiesi@0: # ini_set('pcre.recursion_limit', 200000);
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * Drupal automatically generates a unique session cookie name for each site
danielebarchiesi@0:  * based on its full domain name. If you have multiple domains pointing at the
danielebarchiesi@0:  * same Drupal site, you can either redirect them all to a single domain (see
danielebarchiesi@0:  * comment in .htaccess), or uncomment the line below and specify their shared
danielebarchiesi@0:  * base domain. Doing so assures that users remain logged in as they cross
danielebarchiesi@0:  * between your various domains. Make sure to always start the $cookie_domain
danielebarchiesi@0:  * with a leading dot, as per RFC 2109.
danielebarchiesi@0:  */
danielebarchiesi@0: # $cookie_domain = '.example.com';
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * Variable overrides:
danielebarchiesi@0:  *
danielebarchiesi@0:  * To override specific entries in the 'variable' table for this site,
danielebarchiesi@0:  * set them here. You usually don't need to use this feature. This is
danielebarchiesi@0:  * useful in a configuration file for a vhost or directory, rather than
danielebarchiesi@0:  * the default settings.php. Any configuration setting from the 'variable'
danielebarchiesi@0:  * table can be given a new value. Note that any values you provide in
danielebarchiesi@0:  * these variable overrides will not be modifiable from the Drupal
danielebarchiesi@0:  * administration interface.
danielebarchiesi@0:  *
danielebarchiesi@0:  * The following overrides are examples:
danielebarchiesi@0:  * - site_name: Defines the site's name.
danielebarchiesi@0:  * - theme_default: Defines the default theme for this site.
danielebarchiesi@0:  * - anonymous: Defines the human-readable name of anonymous users.
danielebarchiesi@0:  * Remove the leading hash signs to enable.
danielebarchiesi@0:  */
danielebarchiesi@0: # $conf['site_name'] = 'My Drupal site';
danielebarchiesi@0: # $conf['theme_default'] = 'garland';
danielebarchiesi@0: # $conf['anonymous'] = 'Visitor';
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * A custom theme can be set for the offline page. This applies when the site
danielebarchiesi@0:  * is explicitly set to maintenance mode through the administration page or when
danielebarchiesi@0:  * the database is inactive due to an error. It can be set through the
danielebarchiesi@0:  * 'maintenance_theme' key. The template file should also be copied into the
danielebarchiesi@0:  * theme. It is located inside 'modules/system/maintenance-page.tpl.php'.
danielebarchiesi@0:  * Note: This setting does not apply to installation and update pages.
danielebarchiesi@0:  */
danielebarchiesi@0: # $conf['maintenance_theme'] = 'bartik';
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * Reverse Proxy Configuration:
danielebarchiesi@0:  *
danielebarchiesi@0:  * Reverse proxy servers are often used to enhance the performance
danielebarchiesi@0:  * of heavily visited sites and may also provide other site caching,
danielebarchiesi@0:  * security, or encryption benefits. In an environment where Drupal
danielebarchiesi@0:  * is behind a reverse proxy, the real IP address of the client should
danielebarchiesi@0:  * be determined such that the correct client IP address is available
danielebarchiesi@0:  * to Drupal's logging, statistics, and access management systems. In
danielebarchiesi@0:  * the most simple scenario, the proxy server will add an
danielebarchiesi@0:  * X-Forwarded-For header to the request that contains the client IP
danielebarchiesi@0:  * address. However, HTTP headers are vulnerable to spoofing, where a
danielebarchiesi@0:  * malicious client could bypass restrictions by setting the
danielebarchiesi@0:  * X-Forwarded-For header directly. Therefore, Drupal's proxy
danielebarchiesi@0:  * configuration requires the IP addresses of all remote proxies to be
danielebarchiesi@0:  * specified in $conf['reverse_proxy_addresses'] to work correctly.
danielebarchiesi@0:  *
danielebarchiesi@0:  * Enable this setting to get Drupal to determine the client IP from
danielebarchiesi@0:  * the X-Forwarded-For header (or $conf['reverse_proxy_header'] if set).
danielebarchiesi@0:  * If you are unsure about this setting, do not have a reverse proxy,
danielebarchiesi@0:  * or Drupal operates in a shared hosting environment, this setting
danielebarchiesi@0:  * should remain commented out.
danielebarchiesi@0:  *
danielebarchiesi@0:  * In order for this setting to be used you must specify every possible
danielebarchiesi@0:  * reverse proxy IP address in $conf['reverse_proxy_addresses'].
danielebarchiesi@0:  * If a complete list of reverse proxies is not available in your
danielebarchiesi@0:  * environment (for example, if you use a CDN) you may set the
danielebarchiesi@0:  * $_SERVER['REMOTE_ADDR'] variable directly in settings.php.
danielebarchiesi@0:  * Be aware, however, that it is likely that this would allow IP
danielebarchiesi@0:  * address spoofing unless more advanced precautions are taken.
danielebarchiesi@0:  */
danielebarchiesi@0: # $conf['reverse_proxy'] = TRUE;
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * Specify every reverse proxy IP address in your environment.
danielebarchiesi@0:  * This setting is required if $conf['reverse_proxy'] is TRUE.
danielebarchiesi@0:  */
danielebarchiesi@0: # $conf['reverse_proxy_addresses'] = array('a.b.c.d', ...);
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * Set this value if your proxy server sends the client IP in a header
danielebarchiesi@0:  * other than X-Forwarded-For.
danielebarchiesi@0:  */
danielebarchiesi@0: # $conf['reverse_proxy_header'] = 'HTTP_X_CLUSTER_CLIENT_IP';
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * Page caching:
danielebarchiesi@0:  *
danielebarchiesi@0:  * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page
danielebarchiesi@0:  * views. This tells a HTTP proxy that it may return a page from its local
danielebarchiesi@0:  * cache without contacting the web server, if the user sends the same Cookie
danielebarchiesi@0:  * header as the user who originally requested the cached page. Without "Vary:
danielebarchiesi@0:  * Cookie", authenticated users would also be served the anonymous page from
danielebarchiesi@0:  * the cache. If the site has mostly anonymous users except a few known
danielebarchiesi@0:  * editors/administrators, the Vary header can be omitted. This allows for
danielebarchiesi@0:  * better caching in HTTP proxies (including reverse proxies), i.e. even if
danielebarchiesi@0:  * clients send different cookies, they still get content served from the cache.
danielebarchiesi@0:  * However, authenticated users should access the site directly (i.e. not use an
danielebarchiesi@0:  * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid
danielebarchiesi@0:  * getting cached pages from the proxy.
danielebarchiesi@0:  */
danielebarchiesi@0: # $conf['omit_vary_cookie'] = TRUE;
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * CSS/JS aggregated file gzip compression:
danielebarchiesi@0:  *
danielebarchiesi@0:  * By default, when CSS or JS aggregation and clean URLs are enabled Drupal will
danielebarchiesi@0:  * store a gzip compressed (.gz) copy of the aggregated files. If this file is
danielebarchiesi@0:  * available then rewrite rules in the default .htaccess file will serve these
danielebarchiesi@0:  * files to browsers that accept gzip encoded content. This allows pages to load
danielebarchiesi@0:  * faster for these users and has minimal impact on server load. If you are
danielebarchiesi@0:  * using a webserver other than Apache httpd, or a caching reverse proxy that is
danielebarchiesi@0:  * configured to cache and compress these files itself you may want to uncomment
danielebarchiesi@0:  * one or both of the below lines, which will prevent gzip files being stored.
danielebarchiesi@0:  */
danielebarchiesi@0: # $conf['css_gzip_compression'] = FALSE;
danielebarchiesi@0: # $conf['js_gzip_compression'] = FALSE;
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * String overrides:
danielebarchiesi@0:  *
danielebarchiesi@0:  * To override specific strings on your site with or without enabling the Locale
danielebarchiesi@0:  * module, add an entry to this list. This functionality allows you to change
danielebarchiesi@0:  * a small number of your site's default English language interface strings.
danielebarchiesi@0:  *
danielebarchiesi@0:  * Remove the leading hash signs to enable.
danielebarchiesi@0:  */
danielebarchiesi@0: # $conf['locale_custom_strings_en'][''] = array(
danielebarchiesi@0: #   'forum'      => 'Discussion board',
danielebarchiesi@0: #   '@count min' => '@count minutes',
danielebarchiesi@0: # );
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  *
danielebarchiesi@0:  * IP blocking:
danielebarchiesi@0:  *
danielebarchiesi@0:  * To bypass database queries for denied IP addresses, use this setting.
danielebarchiesi@0:  * Drupal queries the {blocked_ips} table by default on every page request
danielebarchiesi@0:  * for both authenticated and anonymous users. This allows the system to
danielebarchiesi@0:  * block IP addresses from within the administrative interface and before any
danielebarchiesi@0:  * modules are loaded. However on high traffic websites you may want to avoid
danielebarchiesi@0:  * this query, allowing you to bypass database access altogether for anonymous
danielebarchiesi@0:  * users under certain caching configurations.
danielebarchiesi@0:  *
danielebarchiesi@0:  * If using this setting, you will need to add back any IP addresses which
danielebarchiesi@0:  * you may have blocked via the administrative interface. Each element of this
danielebarchiesi@0:  * array represents a blocked IP address. Uncommenting the array and leaving it
danielebarchiesi@0:  * empty will have the effect of disabling IP blocking on your site.
danielebarchiesi@0:  *
danielebarchiesi@0:  * Remove the leading hash signs to enable.
danielebarchiesi@0:  */
danielebarchiesi@0: # $conf['blocked_ips'] = array(
danielebarchiesi@0: #   'a.b.c.d',
danielebarchiesi@0: # );
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * Fast 404 pages:
danielebarchiesi@0:  *
danielebarchiesi@0:  * Drupal can generate fully themed 404 pages. However, some of these responses
danielebarchiesi@0:  * are for images or other resource files that are not displayed to the user.
danielebarchiesi@0:  * This can waste bandwidth, and also generate server load.
danielebarchiesi@0:  *
danielebarchiesi@0:  * The options below return a simple, fast 404 page for URLs matching a
danielebarchiesi@0:  * specific pattern:
danielebarchiesi@0:  * - 404_fast_paths_exclude: A regular expression to match paths to exclude,
danielebarchiesi@0:  *   such as images generated by image styles, or dynamically-resized images.
danielebarchiesi@0:  *   If you need to add more paths, you can add '|path' to the expression.
danielebarchiesi@0:  * - 404_fast_paths: A regular expression to match paths that should return a
danielebarchiesi@0:  *   simple 404 page, rather than the fully themed 404 page. If you don't have
danielebarchiesi@0:  *   any aliases ending in htm or html you can add '|s?html?' to the expression.
danielebarchiesi@0:  * - 404_fast_html: The html to return for simple 404 pages.
danielebarchiesi@0:  *
danielebarchiesi@0:  * Add leading hash signs if you would like to disable this functionality.
danielebarchiesi@0:  */
danielebarchiesi@0: $conf['404_fast_paths_exclude'] = '/\/(?:styles)\//';
danielebarchiesi@0: $conf['404_fast_paths'] = '/\.(?:txt|png|gif|jpe?g|css|js|ico|swf|flv|cgi|bat|pl|dll|exe|asp)$/i';
danielebarchiesi@0: $conf['404_fast_html'] = '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><title>404 Not Found</title></head><body><h1>Not Found</h1><p>The requested URL "@path" was not found on this server.</p></body></html>';
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * By default the page request process will return a fast 404 page for missing
danielebarchiesi@0:  * files if they match the regular expression set in '404_fast_paths' and not
danielebarchiesi@0:  * '404_fast_paths_exclude' above. 404 errors will simultaneously be logged in
danielebarchiesi@0:  * the Drupal system log.
danielebarchiesi@0:  *
danielebarchiesi@0:  * You can choose to return a fast 404 page earlier for missing pages (as soon
danielebarchiesi@0:  * as settings.php is loaded) by uncommenting the line below. This speeds up
danielebarchiesi@0:  * server response time when loading 404 error pages and prevents the 404 error
danielebarchiesi@0:  * from being logged in the Drupal system log. In order to prevent valid pages
danielebarchiesi@0:  * such as image styles and other generated content that may match the
danielebarchiesi@0:  * '404_fast_html' regular expression from returning 404 errors, it is necessary
danielebarchiesi@0:  * to add them to the '404_fast_paths_exclude' regular expression above. Make
danielebarchiesi@0:  * sure that you understand the effects of this feature before uncommenting the
danielebarchiesi@0:  * line below.
danielebarchiesi@0:  */
danielebarchiesi@0: # drupal_fast_404();
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * External access proxy settings:
danielebarchiesi@0:  *
danielebarchiesi@0:  * If your site must access the Internet via a web proxy then you can enter
danielebarchiesi@0:  * the proxy settings here. Currently only basic authentication is supported
danielebarchiesi@0:  * by using the username and password variables. The proxy_user_agent variable
danielebarchiesi@0:  * can be set to NULL for proxies that require no User-Agent header or to a
danielebarchiesi@0:  * non-empty string for proxies that limit requests to a specific agent. The
danielebarchiesi@0:  * proxy_exceptions variable is an array of host names to be accessed directly,
danielebarchiesi@0:  * not via proxy.
danielebarchiesi@0:  */
danielebarchiesi@0: # $conf['proxy_server'] = '';
danielebarchiesi@0: # $conf['proxy_port'] = 8080;
danielebarchiesi@0: # $conf['proxy_username'] = '';
danielebarchiesi@0: # $conf['proxy_password'] = '';
danielebarchiesi@0: # $conf['proxy_user_agent'] = '';
danielebarchiesi@0: # $conf['proxy_exceptions'] = array('127.0.0.1', 'localhost');
danielebarchiesi@0: 
danielebarchiesi@0: /**
danielebarchiesi@0:  * Authorized file system operations:
danielebarchiesi@0:  *
danielebarchiesi@0:  * The Update manager module included with Drupal provides a mechanism for
danielebarchiesi@0:  * site administrators to securely install missing updates for the site
danielebarchiesi@0:  * directly through the web user interface. On securely-configured servers,
danielebarchiesi@0:  * the Update manager will require the administrator to provide SSH or FTP
danielebarchiesi@0:  * credentials before allowing the installation to proceed; this allows the
danielebarchiesi@0:  * site to update the new files as the user who owns all the Drupal files,
danielebarchiesi@0:  * instead of as the user the webserver is running as. On servers where the
danielebarchiesi@0:  * webserver user is itself the owner of the Drupal files, the administrator
danielebarchiesi@0:  * will not be prompted for SSH or FTP credentials (note that these server
danielebarchiesi@0:  * setups are common on shared hosting, but are inherently insecure).
danielebarchiesi@0:  *
danielebarchiesi@0:  * Some sites might wish to disable the above functionality, and only update
danielebarchiesi@0:  * the code directly via SSH or FTP themselves. This setting completely
danielebarchiesi@0:  * disables all functionality related to these authorized file operations.
danielebarchiesi@0:  *
danielebarchiesi@0:  * @see http://drupal.org/node/244924
danielebarchiesi@0:  *
danielebarchiesi@0:  * Remove the leading hash signs to disable.
danielebarchiesi@0:  */
danielebarchiesi@0: # $conf['allow_authorize_operations'] = FALSE;