https://bz.apache.org/bugzilla/show_bug.cgi?id=69871
Bug ID: 69871
Summary: RewriteValve logging silent even when level=ALL;
missing output for rule evaluation / permission
failure
Product: Tomcat 10
Version: 10.1.34
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Catalina
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ------
--------------------
- PROBLEM
--------------------
When RewriteValve cannot read its rewrite.config file due to file permission
issues (root.root ownership, not readable by Tomcat user), no error or warning
is emitted to catalina.out.
The Valve silently fails to apply rewrite rules.
Even with RewriteValve logging set to FINE or ALL, no trace of initialization
or rule evaluation appears. This makes diagnosing configuration/permission
problems difficult.
--------------------
- Expected Behavior:
--------------------
RewriteValve should at least log a warning or error (e.g., “Failed to read
rewrite.config – permission denied”) when configuration cannot be loaded.
--------------------
- Steps to Reproduce:
--------------------
Deploy Tomcat 10.1.34 with RewriteValve declared in context.xml.
Create a WEB-INF/rewrite.config file owned by root:root and not readable by the
Tomcat process user.
Start Tomcat and observe that rewrite rules are not applied.
Check catalina.out — no messages from RewriteValve are logged, even with
logging level = ALL.
--------------------
- Actual Behavior:
--------------------
RewriteValve silently fails with no log output.
--------------------
- Expected Behavior:
--------------------
Should log a clear permission-related error or at least a configuration load
failure.
--------------------
- Additional Info:
--------------------
Tested locally and on AWS (Debian, Tomcat 10.1.34).
Same configuration and rules work correctly when the file is readable.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
