libapache2-mod-rpaf has wrong name in conf file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libapache2-mod-rpaf (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Louis Bouchard |
Bug Description
SRU justification :
rpaf module is not correctly enabled without this modification
Impact :
rpaf module not working as expected
Fix :
Backport Quantal syntax used for that module which correctly set the module name
to rpaf_module
Test Case :
The file /etc/apache2/
<IfModule rpaf_module>
RPAFenable On
RPAFsethostname On
RPAFproxy_ips 127.0.0.1 ::1
</IfModule>
Regression :
None, this modification is already in Quantal and only implemented if
libapache2-mod-rpaf is in use.
Original description of the problem :
In the file /etc/apache2/
<IfModule mod_rpaf.c>
which is for Apache 1.3 but the modules is called mod_rpaf-2.0.c for Apache 2.x, so it must be
<IfModule mod_rpaf-2.0.c>
Here
you can see, that mod_rpaf-2.0.c is compiled and renamed to mod_rpaf.so:
apxs2 -c -o mod_rpaf.so mod_rpaf-2.0.c
Related branches
Changed in libapache2-mod-rpaf (Ubuntu Precise): | |
assignee: | nobody → Louis Bouchard (louis-bouchard) |
status: | Confirmed → In Progress |
tags: |
added: verification-done removed: verification-needed |
libapache2-mod-rpaf (0.6-3) unstable; urgency=low
* Fixed module naming stuff in rpaf.conf (Thanks to Alexander
Kuznetsov). Closes: #653330.
[...]
This fix is in The Quantal Quetzal (current stable release).