Bug 463757 - configuration files web.xml from tomcat5-webapps are not marked %config
configuration files web.xml from tomcat5-webapps are not marked %config
Status: NEW
Product: Red Hat Application Server
Classification: Retired
Component: tomcat5 (Show other bugs)
2.0
All Linux
medium Severity low
: ---
: ---
Assigned To: Ted Ross
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-09-24 11:26 EDT by Karel Volný
Modified: 2014-12-01 18:15 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Karel Volný 2008-09-24 11:26:45 EDT
Description of problem:
In the '%files webapps' section of the tomcat5 .spec file, no file is marked %config, and thus all the web.inf files used for configuring the webapps do not get handled properly by rpm.

For example the file /usr/share/tomcat5/webapps/webdav/WEB-INF/web.xml is used for configuring the webdav access, but it gets overwritten on package upgrade.

Reading the main tomcat configuration file /etc/tomcat5/web.xml there is a comment:

  <!-- WARNING:  Do not configure application-specific resources here!      -->
  <!-- They should go in the "/WEB-INF/web.xml" file in your application.   -->

which would indicate that /usr/share/tomcat5/webapps/*/WEB-INF/web.xml is the place for user configuration, and so that it should not be destroyed by the system.

And BTW, how does that come that *any* configuration files are stored under /usr/share ?

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. Install some old version of tomcat5-webapps
2. Enable the webdav extension by removing the comment marks in the appropriate section of the file /usr/share/tomcat5/webapps/webdav/WEB-INF/web.xml
3. Restart tomcat5 service
4. Send some valid write request to http://yourserver:8080/webdav
5. You get 200 OK in response
6. Upgrade the tomcat5-webapps package
7. Restart tomcat5 service
8. Send some valid write request to http://yourserver:8080/webdav
  
Actual results:
you get 403 Forbidden in response

Expected results:
you get 200 OK in response

Additional info:

Note You need to log in before you can comment on or make changes to this bug.