configure apache to accept request form specific IP
Hi,
What should I change in the httpd.conf so that the apache will accept request from page from specific IP and deny all the rest IP.
I am reading the document of the apache but it is very long (700 pages) and I searched but I could not find something about this.
So if someone can explain me how to do this specific thing, I will be glad?
The direction that I think about is:
while IP1 and IP2 are replaced with the IP numbers that I want to allow.
However I want to make sure it will reject all other IP request.
Hello all,
I have several vhost and not sure which vhost is serving the requests to my url
http://www.mydomain.tld i have ssh access to the web server
is there a way e.g curl to know exactly which vhost served the request.
one of my friend suggested logs but i want to find another... (4 Replies)
Hi All,
I have below perl script which writes xml from .xls file.
Now i want to add below two conditions in this script :
1. to check if the the input .xls file has ony two columns , if more tahn two columns then script should pop up an error.
2. If there are two columns , then first column... (4 Replies)
Is it possible to configure a Solaris server to authenticate users against an Active Directory server when logging in via ssh?
I've seen some docs out there, I've followed their instructions, but it does not work. And I'm beginning to wonder if it is possible or even supported by Oracle. The... (2 Replies)
Hi all,
I have 2 files, One file contain data like this
FHIT
CS
CHRM1
PDE3A
PDE3B
HSP90AA1
PTK2
HTR1A
ESR1
PARP1
PLA2G1B
These names are mentioned in the second file(Please see attached second file) as
# Drug_Target_X_Gene_Name:(Where X can be any number (1-1000) (1 Reply)
Please pardon my ignorance, but I need to create a web-based form which can be used to request access to the unix servers in our environment. It just needs to have input fields for basic info (name, dept., etc.), and perhaps a drop-down box with the names of the servers. The form will be submitted... (2 Replies)
Hello,
I am using apache 2.2 and I need to have certain http requests (those including example.com for instance) to be executed normally and forwarded to another server.
With mod_rewrite, I could easily forward but then the input request would not be executed on my server. Right?
Am I... (1 Reply)
Hello all.
I am trying to compile Apache 2 (again!) and the configure script keeps telling me it does not recognize the options. Everything I am including is in the --help list.
For example: --enable-so. First I will put in the LD flags, then configure with the --enable-so option.
... (2 Replies)
Hello, i want to know the basics to configure prefork.c module
to high Apache performance and i think it's depends on the server hardware details (RAM and Processors)
Thanks :) (0 Replies)
Hi,
I got a script which sends the Email to the user based on certain variables received from Tivoli Server Monitoring 6.1.
Now to keep track of the mails I have wrote a stored procedure in DB2 as we use DB2 UDB as back end which take the variables that were used to send the mail and store it... (3 Replies)
OCF_HEARTBEAT_APACHE(7) OCF resource agents OCF_HEARTBEAT_APACHE(7)NAME
ocf_heartbeat_apache - Manages an Apache web server instance
SYNOPSIS
apache [start | stop | status | monitor | meta-data | validate-all]
DESCRIPTION
This is the resource agent for the Apache web server. This resource agent operates both version 1.x and version 2.x Apache servers.
The start operation ends with a loop in which monitor is repeatedly called to make sure that the server started and that it is operational.
Hence, if the monitor operation does not succeed within the start operation timeout, the apache resource will end with an error status.
The monitor operation by default loads the server status page which depends on the mod_status module and the corresponding configuration
file (usually /etc/apache2/mod_status.conf). Make sure that the server status page works and that the access is allowed *only* from
localhost (address 127.0.0.1). See the statusurl and testregex attributes for more details.
See also http://httpd.apache.org/
SUPPORTED PARAMETERS
configfile
The full pathname of the Apache configuration file. This file is parsed to provide defaults for various other resource agent
parameters. (unique, optional, string, default /etc/apache2/httpd.conf)
httpd
The full pathname of the httpd binary (optional). (optional, string, default /usr/sbin/httpd)
port
A port number that we can probe for status information using the statusurl. This will default to the port number found in the
configuration file, or 80, if none can be found in the configuration file. .sp
(optional, integer, no default)
statusurl
The URL to monitor (the apache server status page by default). If left unspecified, it will be inferred from the apache configuration
file. .sp If you set this, make sure that it succeeds *only* from the localhost (127.0.0.1). Otherwise, it may happen that the cluster
complains about the resource being active on multiple nodes. (optional, string, no default)
testregex
Regular expression to match in the output of statusurl. Case insensitive. (optional, string, default exists, but impossible to show in
a human readable format (try grep testregex))
client
Client to use to query to Apache. If not specified, the RA will try to find one on the system. Currently, wget and curl are supported.
For example, you can set this parameter to "curl" if you prefer that to wget. (optional, string, no default)
testurl
URL to test. If it does not start with "http", then it's considered to be relative to the Listen address. (optional, string, no
default)
testregex10
Regular expression to match in the output of testurl. Case insensitive. (optional, string, no default)
testconffile
A file which contains test configuration. Could be useful if you have to check more than one web application or in case sensitive info
should be passed as arguments (passwords). Furthermore, using a config file is the only way to specify certain parameters. .sp Please
see README.webapps for examples and file description. (optional, string, no default)
testname
Name of the test within the test configuration file. (optional, string, no default)
options
Extra options to apply when starting apache. See man httpd(8). (optional, string, no default)
envfiles
Files (one or more) which contain extra environment variables. If you want to prevent script from reading the default file, set this
parameter to empty string. (optional, string, default /etc/apache2/envvars)
SUPPORTED ACTIONS
This resource agent supports the following actions (operations):
start
Starts the resource. Suggested minimum timeout: 40s.
stop
Stops the resource. Suggested minimum timeout: 60s.
status
Performs a status check. Suggested minimum timeout: 30s.
monitor
Performs a detailed status check. Suggested minimum timeout: 20s. Suggested interval: 10.
meta-data
Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5.
validate-all
Performs a validation of the resource configuration. Suggested minimum timeout: 5.
EXAMPLE
The following is an example configuration for a apache resource using the crm(8) shell:
primitive p_apache ocf:heartbeat:apache
op monitor depth="0" timeout="20s" interval="10"
SEE ALSO
http://www.linux-ha.org/wiki/apache_(resource_agent)
AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors)
resource-agents UNKNOWN 03/09/2014 OCF_HEARTBEAT_APACHE(7)