You have been redirected from an outdated version of the article. Below is the content available on this topic. To view the old article click here.

Request Logging

Structr can be instructed to log all incoming and outgoing requests, including the actual HTTP body. This can be very useful when trying to debug certain aspects of an application, for example to find out whether a mobile client sends / receives the correct data etc.

Request logging can be enabled using the following configuration setting in the structr.conf.

# Set to true to enable full request logging including request body
log.requests = true
log.name = structr-yyyy_mm_dd.request.log

Please note that Structr has to be stopped and restarted in order for the configuration settings to take effect.

Search results for "Request Logging"

Logging

nodeextender.log Enables the logging of generated Java code of the dynamic schema entities to the logfile. This setting allows you to investigate and debug the generation of Java code for your schema entities in cases where something goes wrong.
nodeextender.log.errors Enables the logging of Java compilation errors when compiling the dynamic schema of your application.
log.requests Enables full request logging for all requests handled by Structr. Caution, the log file can get very large when a lot of requests with lots of content are made.
log.debug Controls the debug() built-in function, which will behave exactly like the log() function if enabled.
log.functions.stacktrace Enables stacktrace logging for script calls and built-in functions. If enabled, a scripting error will write the full Java stack trace to the logfile.
log.prefix Sets the prefix for the request log file that is written when log.requests is enabled.
log.javascript.exception.request Adds path, queryString and parameterMap to JavaScript exceptions (if available) if enabled.
log.directorywatchservice.scanquietly Prevents logging of each scan process for every folder processed by the directory watch service.