Topic: Trouble enabling SSI in Apache/2.2.6 (Win32) - ALL SET!

[memnoch]

Hello Fellow Apacherians,

This is a newbie question....thanks for any assistance you could give.

I have Apache/2.2.6 (Win32) installed on XP, and I'm trying to enable SSI but running into trouble. Here's what I have:

- mod_include.so *is* in the modules directory
- in httpd.conf I have:

[glsmith]

You have something else listening on port 80 ... maybe IIS?

[memnoch]

Thanks glsmith....I forgot to mention (now updated above) that the above problem occurs only when I have added the indicated lines in httpd.conf to enable SSI. If I comment them out, Apache works fine. So, I don't think it's due to using port 80. Any other ideas?

[tdonovan]

It is very odd that when you enable SSI (which has nothing to do with sockets) you get symptoms of Winsock2 corruption, like the kind described here.

Some things you could try:

* Open the Windows Task Manager [Ctrl-Shift-Esc] "Processes" tab and check that there are no httpd processes running before you start Apache.

* Comment out any LoadModule directives that you don't need (especially any 3rd-party modules) - in case the problem is insufficient memory or memory address conflicts.

* Remove your AddHandler directive and use these directives instead:

Code:

AddType text/html .shtml AddOutputFilter INCLUDES .shtml


* Add the Win32DisableAcceptEx directive to your httpd.conf file - in case you have some 3rd-party network software which interferes with the Windows AcceptEx function.

I hope one of these suggestions helps.

-tom-

[memnoch]

Thanks Tom....that seems to have helped. Here's what I found:

- There were no httpd processes running before I started Apache.

- The only LoadModules enabled, aside from what comes enabled by default, was for mod_per:

LoadFile "C:/Perl/bin/perl58.dll"
LoadModule perl_module modules/mod_perl.so

which had worked fine without SSI anyway.

- I replaced my AddHandler with the directives you specified, and restarted Apache....it seems to work now.

- I haven't done anything yet with Win32DisableAcceptEx yet.

I have done some more testing and see that even with your changes, I started getting the same error again. It seems that if Apache is UP and I run "httpd -k restart", I get the error. But if instead I run "httpd -k stop" followed by "httpd -k start", it works fine. Any comments?

I also see that I had been looking at the Apache 1.3 documentation when I added the AddHandler directive. I now see that the 2.2 documentation has the directives you mentioned.

One other question, though. The httpd.conf file also has the following has the AddType and AddOutputFilter directives inside of the <IfModule mime_module> container. Right now, I have those commented out, and the have them enabled in the <Directory "C:/Apache2/htdocs"> container...does this matter?

Thank you very much!

memnoch

[tdonovan]

I have also noticed that Apache 2.2.6 can not do a graceful restart when mod_perl is loaded. "httpd -k stop" followed by "httpd -k start" is the way to go until this gets fixed.

I found a coding error in mod_perl and reported a bug (and proposed patch) to the mod_perl list here. Coincidentally, this was just a few days ago.

re: "inside of the <IfModule mime_module> container"
The only advantage to putting these directives inside a <IfModule mime_module> container is that if you remove (or comment out) the LoadModule for mod_mime, these statements will be skipped - so you don't need to remove them too. Not a big advantage unless you think you will be enabling/disabling SSI frequently.

FYI - You can put the <IfModule mime_module>...</IfModule> container inside your <Directory "C:/Apache2/htdocs">...</Directory> container if you want to.

-tom-

[memnoch]

Tom...thank you so much....I'm glad you had found that mod_perl defect!

memnoch