Start line:  
End line:  

Snippet Preview

Snippet HTML Code

Stack Overflow Questions
access.log.enabled.description=Whether to enable Access logging or not.
access.log.enabled.name=Enable Access Log
access.log.output.description=Name of the destination for the request log. The access log writes an entry for each request as the request terminates using the NCSA extended/combined log format. In terms of Request Logger Service formats the access log is written with the format "%h %l %u %t "%r" %>s %b "%{Referer}i" "%{User-Agent}i"".
access.log.output.name=Access Log Name
access.log.outputtype.description=Type of access log destination. Select "Logger Name" to write the access log to an SLF4J logger, "File Name" to write the access log to a file (relative paths resolved against sling.home) or "RequestLog Service" to use a named OSGi service registered with the service interface "org.apache.sling.engine.RequestLog" and a service property "requestlog.name" equal to the Logger Name setting.
access.log.outputtype.name=Access Log Type
request.log.description=Configures the main loggers of the request logger, namely the request log and the access log. Further loggers may be configured by creating configurations for the Request Logger Service.
request.log.enabled.description=Whether to enable Request logging or not.
request.log.enabled.name=Enable Request Log
request.log.name=Apache Sling Request Logger
request.log.output.description=Name of the destination for the request log. The request log logs the entry and exit of each request into and out of the system together with the entry time, exit time, time to process the request, a request counter as well as the final status code and response content type. In terms of Request Logger Service formats, request entry is logged with the format "%t [%R] -> %m %U%q %H" and request exit is logged with the format "%{end}t [%R] <- %s %{Content-Type}o %Dms".
request.log.output.name=Request Log Name
request.log.outputtype.description=Type of request log destination. Select "Logger Name" to write the access log to an SLF4J logger, "File Name" to write the access log to a file (relative paths resolved against sling.home) or "RequestLog Service" to use a named OSGi service registered with the service interface "org.apache.sling.engine.RequestLog" and a service property "requestlog.name" equal to the Logger Name setting.
request.log.outputtype.name=Request Log Type
request.log.service.description=This configuration creates customizable loggers for request content. Each configuration results in a logger writing the requested data. Deleting an existing configuration removes the respective logger.
request.log.service.format.description=The format for log entries. This is a format string as defined at http://sling.apache.org/site/client-request-logging.html#ClientRequestLogging-LogFormatSpecification.
request.log.service.format.name=Log Format
request.log.service.name=Apache Sling Customizable Request Data Logger
request.log.service.onentry.description=Check if the logger is called on request entry. Otherwise leave unchecked and the logger will be called on request exit (aka termination), which is the default for access logger type loggers.
request.log.service.onentry.name=Request Entry
request.log.service.output.description=Name of the destination for the log output. Depending on the output type this is a file name (absolute or relative), a SLF4J logger name or the name under which a RequestLog service has been registered.
request.log.service.output.name=Logger Name
request.log.service.outputtype.description=Type of log destination. Select "Logger Name" to write the access log to an SLF4J logger, "File Name" to write the access log to a file (relative paths resolved against sling.home) or "RequestLog Service" to use a named OSGi service registered with the service interface "org.apache.sling.engine.RequestLog" and a service property "requestlog.name" equal to the Logger Name setting.
request.log.service.outputtype.name=Logger Type
sling.default.parameter.encoding.description=The default request parameter encoding used to decode request parameters into strings. If this property is not set the default encoding is "ISO-8859-1" as mandated by the Servlet API spec. This default encoding is used if the "_charset_" request parameter is not set to another (supported) character encoding. Applications being sure to always use the same encoding (e.g. UTF-8) can set this default here and may omit the "_charset_" request parameter.
sling.default.parameter.encoding.name=Default Parameter Encoding
sling.description=Main processor of the Sling framework controlling all aspects of processing requests inside of Sling, namely authentication, resource resolution, servlet/script resolution and execution of servlets and scripts.
sling.filter.compat.mode.description=This switch controls the handling of servlet filters. By default only filters with a scope property are registered. In compat mode, the scope property is not required.
sling.filter.compat.mode.name=Filter Compat Mode
sling.max.calls.description=Defines the maximum number of Servlet and Script calls while processing a single client request. This number should be high enough to not limit request processing artificially. On the other hand it should not be too high to allow the mechanism to limit the resources required to process a request in case of errors. The default value is 1000.
sling.max.calls.name=Number of Calls per Request
sling.max.inclusions.description=The maximum number of recursive Servlet and Script calls while processing a single client request. This number should not be too high, otherwise StackOverflowErrors may occurr in case of erroneous scripts and servlets. The default value is 50.
sling.max.inclusions.name=Recursion Depth
sling.max.record.requests.description=Defines the number of requests that internally recorded for display on the "Recent Requests" Web Console page. If this value is less than or equal to zero, no requests are internally kept. The default value is 20.
sling.max.record.requests.name=Number of Requests to Record
sling.name=Apache Sling Main Servlet
sling.store.pattern.requests.description=One or more regular expressions which limit the requests which are stored by the "Recent Requests" Web Console page.
sling.store.pattern.requests.name=Recorded Request Path Patterns
sling.trace.allow.description=If set to true, the HTTP TRACE method will be enabled. By default the HTTP TRACE methods is disabled as it can be used in Cross Site Scripting attacks on HTTP servers.
sling.trace.allow.name=Allow the HTTP TRACE method
New to GrepCode? Check out our FAQ X