Hot answers tagged httpd
From the article you linked, there are three recommended steps to protect yourself against this vulnerability. In principle these steps apply to any software you may use with SSL/TLS but here we will deal with the specific steps to apply them to Apache (httpd) since that is the software in question. Disable Export Cipher Suites Dealt with in the ...
Try looking for a <Directory /> section and make sure that any settings within that tag are restrictive. Also check if mod_userdir is enabled and configured. Look for tags like UserDir
Usually, you can't detect broken connection until you start writing back to user. Otherwise, your process will continue doing its work without noticing connection abort from user side. This post is related even if it talks about PHP. The concept should be the same. There are possible things you can try: Do the time-consuming work in background. When a ...
Warning: this information may be obsolete. See last paragraph. I remember having had the same problem, and solving it with a nph (no parse header) CGI script. Normally, apache collects all the headers from your script, and when finished reading headers, amends them with some standard headers you didn't provide. Which also means, as long as you don't finish ...
You need to have an .htaccess file inside /var/www/test/subapp/ and the rewrite rules should be written for that index.php Also try to ignore /subapp/ URL from /var/www/test/.htaccess
Are you experiencing any site performance issues? The thing with Linux is that it's not a bad thing for top to show that all your RAM is in use. Try giving us the output of free -m. When an application is finished with the memory it used, the kernel doesn't immediately purge the pages of data and mark it as free memory again. For instance, my desktop VM I ...
Only top voted, non community-wiki answers of a minimum length are eligible