Tag Info

New answers tagged

0

For most of the log lines you can find the explanation in the apache wiki about proxy abuse. The fifth and fourth from the end, that are 408 as response code are timed out request. Nothing to worry about too much, they are scanning.


8

It's an RFC thing as detailed by Apache. By default, Apache will accept requests even if they contain invalid URIs, but instead the user will be redirected to your server's main page. The CONNECT requests being refused is proper behavior. As detailed in the link above, you can manually block these requests, but there's no immediate need to.


1

It almost looks as if the server is being used as a web proxy. Try disabling port 80 outbound from that IP(internal to external) and see if the logs keep showing up. If not it might be time to look into tightening down your security...


1

I ran into a similar problem while following a tutorial - http://www.tecmint.com/protect-apache-using-mod_security-and-mod_evasive-on-rhel-centos-fedora/ My httpd.conf file already had an include for *.conf and the tutorial had me explicitly include the modsecurity.conf file. As a result, all my rules were duplicates because the conf file was included ...


1

Converting my earlier comment into an answer, to popular demand ;) From the you-learn-something-everyday department: I saw Dan Walsh give a presentation yesterday, in which he explained the new way of disabling confinement for applications in newer releases of Fedora and EL6. You no longer set a boolean to disable transition (which sometimes ...


-2

Use the option --prefix=/etc/httpd with ./configure while installing. ./configure --prefix=/etc/httpd --your-other-options...


1

Fixed Apache directive. Wrong directive: RequestHeader set X_FORWARDED_PROTO 'https' Correct directive: RequestHeader set X-FORWARDED-PROTO 'https' I originally took it from the http://www.redmine.org/projects/redmine/wiki/FAQ#Why-does-Redmine-use-http-links-when-I-want-it-to-use-https-links-in-Apache-SSL and then copied in my Apache config file. I ...


0

OK, finally it works. Here the complete solution (maybe there is some details which are not very clean, but it works). Front server needs a direct access to cas server, mod_auth_cas doesn't support request through a proxy, and cas certificate have to match requested address. On my front http, I setup cas auth auth_cas.conf : <IfModule !mod_ssl.c> ...


0

Had to change httpd.config in /etc/httpd/conf/ from: PidFile run/httpd.pid to: PidFile /var/run/httpd.pid Also, changed httpd file in /etc/sysconfig/ from: PIDFILE=/var/run/httpd/httpd.pid to: PIDFILE=/var/run/httpd.pid Run the following comand: killall -9 httpd then, to remove httpd lock: rm -f /var/lock/subsys/httpd And restarted Apache: service ...


-1

Okay, this is some kind of embarrassing. I forgot to run a2enmod ssl.


0

It seems that you have an application engine, such as PHP, running as root. Verify the user owning the process for each of your server daemons through ps or top.



Top 50 recent answers are included