Page History
...
Property: |
| ||
Example Value: |
| ||
Informational Note: | This is where your logging configuration file is located. You may override the default log4j configuration by providing your own. Existing alternatives are:
| ||
Property: |
| ||
Example value: |
| ||
Informational Note: | This is where to put the logs. (This is used for initial configuration only) | ||
Property: | loglevel.dspace (defined in log4j.properties) | ||
| Example value: | loglevel.dspace = INFO | ||
| Informational Note: | Log level for all DSpace-specific code (org.dspace.* packages). By default, DSpace only provides general INFO logs (in order to keep log sizes reasonable). As necessary, you can temporarily change this setting to any of the following (ordered for most information to least): DEBUG, INFO, WARN, ERROR, FATAL Please be aware we do not recommend running at the DEBUG level in Production for significant periods of time, as it will cause the logs to be extremely large in size. | ||
Property: | loglevel.other (defined in log4j.properties) | ||
| Example value: | loglevel.other = INFO | ||
| Informational Note: | Log level for other third-party tools/APIs used by DSpace (non-DSpace specific code). By default, DSpace only provides general INFO logs (in order to keep log sizes reasonable). As necessary, you can temporarily change this setting to any of the following (ordered for most information to least): DEBUG, INFO, WARN, ERROR, FATAL Please be aware we do not recommend running at the DEBUG level in Production for significant periods of time, as it will cause the logs to be extremely large in size. | ||
Property: |
| ||
Example Value: | |||
Informational Note: | If your DSpace instance is protected by a proxy server, in order for log4j to log the correct IP address of the user rather than of the proxy, it must be configured to look for the X-Forwarded-For header. This feature can be enabled by ensuring this setting is set to true. This also affects IPAuthentication, and should be enabled for that to work properly if your installation uses a proxy server. |
Previous releases of DSpace provided an example ${dspace.dir}/config/log4j.xml as an alternative to log4j.properties. This caused some confusion and has been removed. log4j continues to support both Properties and XML forms of configuration, and you may continue (or begin) to use any form that log4j supports.
...
Property: |
|
Example Value |
|
Informational Note | Enter the host name without the port number. |
Property: |
|
Example Value |
|
| Informational Note | Enter the port number for the proxy server. |
Property |
|
Example Value: |
|
Informational Note: | As of DSpace 7 (and above), this setting defaults to true. If "useProxies" is enabled, the authentication and statistics logging code will read the X-Forwarded-For header in order to determine the correct client IP address. As the User Interface uses Angular Universal (for SEO support), the proxy server that comes with Angular Universal is always enabled. By default, only your local server (127.0.0.1) is "trusted" as a proxy. If your DSpace instance is protected by external proxy server, you may need to update the "proxies.trusted.ipranges" property below. This also affects IPAuthentication, and should be enabled for that to work properly if your installation uses a proxy server. |
Property | proxies.trusted.ipranges |
Example Value: | proxies.trusted.ipranges |
Informational Note: | By default, only proxies running on localhost (127.0.01) are "trusted". This allows our Angular User Interface to communicate with the REST API via a trusted proxy on your local server. Leave this property empty to trust X-Forwarded-For values of all requests. You can specify a range by only listing the first three ip-address blocks, e.g. 128.177.243 If you are running REST & UI on different servers, you should add the UI servers (range) as a proxy. |
Configuring Media Filters
...
Overview
Content Tools