Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Apache 2.0 for RedHat Linux and enabling SSI
talker_ys
Greets:
Experiencing some hurdles around enabling SSI on Apache 2.0 on Linux...hoping someone could shed some light on the matter:
We attempted to use mod_iw_ts_rewrite.so (plugin provided by IWOV) and mod_rewrite.so (out-of-the-box for Apache) and both have been unsuccessful:
Steps taken to enable SSI using mod_iw_ts_rewrite.so as per the install doc and Knowledge Base Article: 2241:
1. httpd -l output
bash-3.00$ /usr/sbin/apachectl -l
Compiled in modules:
core.c
prefork.c
http_core.c
mod_so.c
2. httpd -V output
bash-3.00$ /usr/sbin/apachectl -V
Server version: Apache/2.0.52
Server built: Jan 30 2007 09:56:53
Server's Module Magic Number: 20020903:9
Architecture: 32-bit
Server compiled with....
-D APACHE_MPM_DIR="server/mpm/prefork"
-D APR_HAS_SENDFILE
-D APR_HAS_MMAP
-D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
-D APR_USE_SYSVSEM_SERIALIZE
-D APR_USE_PTHREAD_SERIALIZE
-D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
-D APR_HAS_OTHER_CHILD
-D AP_HAVE_RELIABLE_PIPED_LOGS
-D HTTPD_ROOT="/etc/httpd"
-D SUEXEC_BIN="/usr/sbin/suexec"
-D DEFAULT_PIDLOG="logs/httpd.pid"
-D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
-D DEFAULT_LOCKFILE="logs/accept.lock"
-D DEFAULT_ERRORLOG="logs/error_log"
-D AP_TYPES_CONFIG_FILE="conf/mime.types"
-D SERVER_CONFIG_FILE="conf/httpd.conf"
3. Edit LoadModule section in httpd.conf
LoadModule iw_ts_rewrite_module iw-home/lib/mod_iw_ts_rewrite.so
AddModule mod_iw_ts_rewrite.c
(IMPORTANT NOTE: The AddModule and ClearModuleList directives no longer exist. These directives were used to ensure that modules could be enabled in the correct order. The new Apache 2.0 API allows modules to explicitly specify their ordering, eliminating the need for these directives.)
4. Add the Includes statement to the Directory section of the httpd.conf file as shown in the following example:
Options Indexes FollowSymLinks ExecCGI Includes
AllowOverride None
Order allow,deny
Allow from all
5. Edit the end of the AddModule section of the httpd.conf file as follows:
AddModule mod_iw_ts_rewrite.c
(IMPORTANT NOTE: The AddModule and ClearModuleList directives no longer exist. These directives were used to ensure that modules could be enabled in the correct order. The new Apache 2.0 API allows modules to explicitly specify their ordering, eliminating the need for these directives.)
ERROR message outputted when attempting to restart Apache:
bash-3.00$ /etc/init.d/httpd configtest
Syntax error on line 190 of /etc/httpd/conf/httpd.conf:
Cannot load /iw-home/teamsite/lib/mod_iw_ts_rewrite.so into server: /iw-home/teamsite/lib/mod_iw_ts_rewrite.so: undefined symbol: ap_vsnprintf
Error is within the code of the .so file which is pre-compiled and we are unable to troubleshoot the code...forwarded to IWOV Support.
Steps taken to enable SSI using mod_rewrite.so as per Knowledge Base Article: 51890:
To use mod_rewrite to support SSI, first be sure that mod_rewrite is installed and enabled in your origin server (this is the server on TCP:81 in most installations NOT iw-webd). Next, run the mk_mod_rewrite_conf.ipl program which is attached to this article. This program will read your iw.cfg file and generate a mod_rewrite configuration file based on your [iwproxy_remap] and [iwproxy_plugin_remap] sections. Copy this output to your rewrite.conf file. You should also ensure that you have the following lines in your httpd.conf:
RewriteEngine On
Include [path_to_your_rewrite.conf]/rewrite.conf
Note: the attached mk_mod_rewrite_conf.ipl utility is provided as an aidto customers. It is not a part of any packaged Interwoven software and supportof it is limited.
All these goodies said, lets apply the following steps:
1. Validate mod_rewrite is installed and enabled in the origin server.
2. Add the lines below to the iwproxy area of the iw.cfg file (regex needs to be correct...just winging it here but the debug set to true should hopefully provide us with information in the logs on what the rewrites are doing)
[iwproxy_plugin_remap]
_debug=true
_regex=/var/www/html/(.*)=/iw-mount/default/main/external/axa-equitable/development/WORKAREA/code/$2
3. Run the mk_mod_rewrite_conf.ipl script (find it in KB 51890)
4. Copy output to rewrite.conf
5. Add the lines below in httpd.conf
RewriteEngine On
Include [path_to_your_rewrite.conf]/rewrite.conf
NOTE: Add the lines above to the DocumentRoot Directory sections.
ERROR message outputted when attempting to restart Apache:
"Line 12 in the rewrite.conf is not allowed" which is the following:
RewriteLog "/iw-home/teamsite/local/logs/iwui/rewrite.log"
Commenting out that line doesn't help as it complains about the next line and so forth.
This information is hard-coded in the rewrite.conf.template which we do/have not altered.
Any guidance you may provide would be greatly appreciated, thanks!
Regards,
-Yama
Find more posts tagged with
Comments
talker_ys
My apologies...most important information which I failed to provided. In addition to KB 51890, SSI worked if RewriteEngine and Include directives were not added to the httpd.conf file and include path is relative... and not if absolute.... For absolute, the logs indicate the server is looking at its docroot (/var/www/html) for the include file. Once the RewriteEngine and Include directives were added to the httpd.conf file, failure at restart with the error noted in the message above.
As per the install doc and KB 2241, does seems to work at all. Failure at restart of webserver.
talker_ys
The directions in KB 51890 are not as clear as one would like so further clarification to the steps will be provided here:
Steps to enable SSI using mod_rewrite.so as per Knowledge Base Article: 51890:
To use mod_rewrite to support SSI, first be sure that mod_rewrite is installed and enabled in your origin server (this is the server on TCP:81 in most installations NOT iw-webd). Next, run the mk_mod_rewrite_conf.ipl program which is attached to this article. This program will read your iw.cfg file and generate a mod_rewrite configuration file based on your [iwproxy_remap] and [iwproxy_plugin_remap] sections. Copy this output to your rewrite.conf file. You should also ensure that you have the following lines in your httpd.conf:
RewriteEngine On
Include [path_to_your_rewrite.conf]/rewrite.conf
Note: the attached mk_mod_rewrite_conf.ipl utility is provided as an aidto customers. It is not a part of any packaged Interwoven software and supportof it is limited.
That said, apply the following steps:
1. Validate mod_rewrite is installed and enabled in the origin server (listening on port 81 usually).
2. Run the mk_mod_rewrite_conf.ipl script (find it in KB 51890)
3. Copy output to the rewrite.conf of the origin server, not the iw-webd rewrite.conf. If one does not exist, create it (usually in located in
/conf) and properly reference it in the Include directive below.
4. Add the lines below at the end of the origin web server httpd.conf
RewriteEngine On
Include [path_to_origin_web_server_rewrite.conf]/rewrite.conf
5. Restart the origin web server and iw-webd (./iwreset -a)
That should hopefully do it...if you are still experiencing issues, the regexes defined in the iwproxy_plugin_remap section maybe a possible cause.