Read configuration from AKKA's application.conf
List of root paths from while files can be served.
This is enforced to stop relative path type attacks; e.g. ../etc/passwd
Temporary directory where compressed files can be stored.
Defaults to the java.io.tmpdir system property.
Local in memory cache to store file meta and content. Defaults to storing 1000 items.
Maximum size of file contents to cache in memory
The contents of files under this limit is cached in memory for serverCacheTimeoutSeconds. Requests for this file
will be served by the contents stored in memory rather than the file system.
Files larger than this limit are served by reading from the file system for every request.
Defaults to 100K. 0 indicates that files will not be cached in memory.
Number of seconds file meta data (such as file name, size, timestamp and hash) and file contents will be cached in memory. After this time, cache data will be removed and file meta data will and contents will have to be read from the file system.
Note that if serverCacheMaxFileSize is 0 and serverCacheTimeoutSeconds is > 0, then only file meta data
will be cached in memory.
Defaults to 1 hour. 0 means files will NOT be cached.
Number of seconds before a browser should check back with the server if a file has been updated.
This setting is used to drive the Expires and Cache-Control HTTP headers.
Defaults to 1 hour. 0 means cache headers will not be sent to the browser.
Number of seconds before a browser should check back with the server if a file has been updated.
Number of seconds before a browser should check back with the server if a file has been updated.
This setting is used to drive the Expires and Cache-Control HTTP headers.
Defaults to 1 hour. 0 means cache headers will not be sent to the browser.
Local in memory cache to store file meta and content.
Local in memory cache to store file meta and content. Defaults to storing 1000 items.
List of root paths from while files can be served.
List of root paths from while files can be served.
This is enforced to stop relative path type attacks; e.g. ../etc/passwd
Maximum size of file contents to cache in memory
The contents of files under this limit is cached in memory for serverCacheTimeoutSeconds.
Maximum size of file contents to cache in memory
The contents of files under this limit is cached in memory for serverCacheTimeoutSeconds. Requests for this file
will be served by the contents stored in memory rather than the file system.
Files larger than this limit are served by reading from the file system for every request.
Defaults to 100K. 0 indicates that files will not be cached in memory.
Number of seconds file meta data (such as file name, size, timestamp and hash) and file contents will be cached in memory.
Number of seconds file meta data (such as file name, size, timestamp and hash) and file contents will be cached in memory. After this time, cache data will be removed and file meta data will and contents will have to be read from the file system.
Note that if serverCacheMaxFileSize is 0 and serverCacheTimeoutSeconds is > 0, then only file meta data
will be cached in memory.
Defaults to 1 hour. 0 means files will NOT be cached.
Temporary directory where compressed files can be stored.
Temporary directory where compressed files can be stored.
Defaults to the java.io.tmpdir system property.
Configuration for org.mashupbots.socko.handlers.StaticContentHandler.
This can also be loaded from an externalized AKKA configuration file. For example:
static-content-config { # CSV list of root paths from while files can be served. root-file-paths=/home/me/path1,/home/me/path2 # Temporary directory where compressed files can be stored. # Defaults to the `java.io.tmpdir` system property if setting is omitted temp-dir=localhost # Max number of files and resources to store in the local in memory cache # Defaults to storing 1000 items if setting is omitted server-cache-max-size=1000 # Maximum size of files (in bytes) to be cached. Files larger than this will # not be cached and will be served from the file system or resorce. # Defaults to 100K if setting is omitted server-cache-max-file-size=102400 # Number of seconds files will be cached in local memory # Defaults to 3600 if setting is omitted server-cache-timeout=3600 # Number of seconds before a browser should check back with the server if a file has been updated. # This setting is used to drive the `Expires` and `Cache-Control` HTTP headers. # Defaults to 3600 if setting is omitted browser-cache-timeout=3600 }can be loaded as follows:
List of root paths from while files can be served. This is enforced to stop relative path type attacks; e.g.
../etc/passwdTemporary directory where compressed files can be stored. Defaults to the
java.io.tmpdirsystem property.Local in memory cache to store file meta and content. Defaults to storing 1000 items.
Maximum size of file contents to cache in memory The contents of files under this limit is cached in memory for
serverCacheTimeoutSeconds. Requests for this file will be served by the contents stored in memory rather than the file system.Files larger than this limit are served by reading from the file system for every request.
Defaults to 100K.
0indicates that files will not be cached in memory.Number of seconds file meta data (such as file name, size, timestamp and hash) and file contents will be cached in memory. After this time, cache data will be removed and file meta data will and contents will have to be read from the file system.
Note that if
serverCacheMaxFileSizeis 0 andserverCacheTimeoutSecondsis > 0, then only file meta data will be cached in memory.Defaults to 1 hour.
0means files will NOT be cached.Number of seconds before a browser should check back with the server if a file has been updated.
This setting is used to drive the
ExpiresandCache-ControlHTTP headers.Defaults to 1 hour.
0means cache headers will not be sent to the browser.