Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

I'm an apache newbie need help with a module

Status
Not open for further replies.

fabiangp

Technical User
Aug 10, 2006
17
0
0
US
I need to know where to get mod_proxy.c and how to add it to my apache as a dynamic module. I would like to use it with ntop so I don't need to open another port in my firewall but I couldn't find the file. I found proxy_html_mod and load it but ProxyPass do not work without the mod_proxy.c file. Thanks for your help!!!
 
I'm quite comfortable with my apache, I don's know if it's to old its 2.0.54. I would like to upgrade it but i'm pretty sure I will mess it up. Thanks for your help anyways.
 
2.0.54 would not be considered "very old" as Rhythm is mentioning.

Make sure you have
Code:
LoadModule proxy_module modules/mod_proxy.so
in your httpd.conf

the <IfModule mod_proxy.c> directive just tests to see if mod_proxy.so is loaded.

HTH
Jeb
0\
 
I stand corrected. :) You are looking for a specific file called mod_proxy.c. This method of adding modules hasn't been used for quit a while. Back in the olden days, you would use two directives. First you used LoadModule which loaded the DSO file:

Code:
LoadModule proxy_module modules/mod_proxy.so

Then you used the corresponding AddModule directive:

Code:
AddModule mod_proxy.c

Nowadays, this is all done using just the LoadModule directive. mod_proxy.c is included in the DSO. Look in your modules directory and if it is there, look to see if it is in your httpd.conf. If everything checks out, then the link I provided should be a lot of help.



 
Thanks for your help guys. now, how can I install the newest apache and make sure I leave it exactly as the current one? and even more, I use debian but remember instaalling apache from source, not from a .deb package. Is there any procedure that you can tell me about, so I make sure don't meesss up. More important, Is it worth it?
 
Two of the simplest things are copy config.log from the original build location. This has the original ./configure command line. Also save a copy your httpd.conf file.

Besides that, you can build the newer version to a different destination directory so it doesn't interfere with the original. Just set it to listen on a different port,

When you are happy that it behaves as expected, shut down the original 2.0.54, set the new 2.2.x to listen on 80 and restart it.

Don't know it hte upgrade would be worth it or not...

Jeb
 
the config.log info is what I needed, I didn't know how I built it the first time, and I didn't what to screw it up!! thanks a lot!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top