Overview
Parameter:EXCEPTIONPAGEDETAILS
Category: Default
Default value: 1
Product: eTASK.Portal
What does this parameter do?
This parameter controls whether technical error details such as stack traces and internal system information are displayed on the error page when an unhandled exception occurs.
What is this parameter used for?
Controlling the visibility of technical error information for end users
Preventing information disclosure in production environments
Providing diagnostic information for developers and support
Supporting error analysis through detailed error messages
Technical Details (for Administrators)
Format: Integer
Default value: 1
Valid values:
0= Technical details completely hidden1= Technical details are displayed
Important notes:
When set to
0the copy function for error messages is disabledIf set to
1, stack traces and context information are visible to usersThis setting affects the exception page
When should you change this value?
Set the value to 0 (hide details) if:
The application is running in a production environment
Sensitive system information needs to be protected from end users
Compliance requirements mandate minimizing information disclosure
Security policies prohibit the display of internal details
Set to 1 (Show details) if:
The application is running in a development or test environment
Developers and testers need detailed error information
Support teams need to collect error reports from users
Quick error diagnosis based on complete error messages is required
Important Notes
Production environments
In production environments, this value should always be set to0to protect sensitive information.Development and test environments
The default value1enables efficient error analysis and should be retained in non-production environments.Support
scenarios1users can forward detailed error messages to support using the copy function, which speeds up problem resolution.Logging remains active
Regardless of this parameter, errors are still recorded in the system log. The parameter only affects the display for the end user.
Security
Does changing this parameter affect security?
Yes, a change has a direct impact on security due to information disclosure.
When set to
1, stack traces are displayed that may reveal file structures, methods, and database connectionsAttackers can use technical details to gather information about the system architecture and potential vulnerabilities
When set to
0information disclosure is prevented by displaying only generic error messages
Conclusion: The parameter is security-relevant. In production environments, the value should be set to 0 to prevent information disclosure. In development environments, the value 1 efficient error analysis.
Practical example
Initial situation:
A production installation has EXCEPTIONPAGEDETAILS set to the default value 1. In the event of an error, users see the complete stack trace with file structures and database connections.
Configuration:
The administrator sets EXCEPTIONPAGEDETAILS to 0.
After the change:
If an error occurs, only a generic error message is displayed
The copy function for technical details is no longer available
End users no longer see sensitive system information
Error details are still recorded in the system log and are available to administrators
Result:
Increased security by preventing information disclosure while maintaining complete error logging for administrative purposes.
Recommended setting
For standard installations:0(Production environment)
Reason:
Prevents information disclosure and protects against the unintended disclosure of system information
Complies with best practices for production environments
Error analysis remains possible via system logs
Exceptions (development/test environments):
Value
1is useful for providing developers and testers with complete error informationAccelerates error diagnosis through direct visibility of stack traces
Tip: Use different configurations for different environments. Production: 0, Test/Development: 1.