I am attempting to add virtual hosts to an apache web server, which has this current configuration:
I have been trying to add a configuration like this, based off another working server:
...but it totally ignores the new configuration, going straight to /var/www in defiance of the new virtualhost whenever subname.servername.com is accessed. So I get the 'it works!' page, instead of someone's particular wordpress instance.
I can tell it's at least reading the configuration though, since adding the virtualhost somehow breaks apache's ability to follow symbolic links.
Would this be the correct entry for Apache to answer on the IP 129.250.242.126 if the servers IP is 129.250.242.125? Are any other changes necessary to get Apache to answer this IP for web traffic?
< VirtualHost 129.250.242.126>
ServerName www.my_domain.com
ServerAdmin admin@my_domain.com... (4 Replies)
I am currently going through the servers in our network and trying to compile a list of the current aliases for each box and any virtual IP addresses. I can check for the ones that are supposed to be there but how do I list the ones that I don't even know exist?
ANY help would be greatly... (1 Reply)
Is it possible to reliably detect the virtual host of a Sun Solaris box, within a shell or Perl script?
Can a system have multiple virtual host or not host at all ?
I was recently made aware of hostname command, but was not sure if this option was the only one available.
Any help is much... (3 Replies)
Hi,
I have set up the following virtual host but it cannot find the URL?
Apache is running fine and I have disabled iptables. Within the document root I have the following file index.html displaying a sample text message.
Any ideas what my problem might be?
httpd.conf:
... (2 Replies)
Trying to set or modify the randomly set hostID of a Solaris 10 virtual/guest machine that I installed on a Windows-XP host machine (using Virtual Box 4.1.12).
I was able to set/modify the hostname of the Solaris 10 virtual/guest machine during installation as well as via the Virtual Box... (4 Replies)
Hi folks,
I recently read about Apache virtual host and was able to configure that as well. I used name based virtual host (lets say http://vhost1.example.com) and it worked just fine. Then I configured another named based virtual host on same apache server (lets say http://vhost2.example.com)... (2 Replies)
Hi folks,
I am trying to configure Apache webserver and also a virtual host inside this webserver.
For Global server config: /var/www/html/index.html
For virtual host config: /var/www/virtual/index.html
Both client10 & www10 are pointing to 192.168.122.10 IP address.
BUT, MY... (1 Reply)
Hello,
I am facing a very strange issue while setting a virtual host on apache to setup multiple websites using separate IPs.
Virtual host is setup but when i am browsing the website it display content under /var/www/html and displaying site1 and site2 folder instead of access the content... (2 Replies)
Discussion started by: sunnysthakur
2 Replies
LEARN ABOUT SUSE
mod_apparmor
MOD_APPARMOR(8) AppArmor MOD_APPARMOR(8)NAME
mod_apparmor - fine-grained AppArmor confinement for Apache
DESCRIPTION
An AppArmor profile applies to an executable program; if a portion of the program needs different access permissions than other portions,
the program can "change hats" via aa_change_hat(2) to a different role, also known as a subprofile. The mod_apparmor Apache module uses
the aa_change_hat(2) mechanism to offer more fine-grained confinement of dynamic elements within Apache such as individual php and perl
scripts, while still allowing the performance benefits of using mod_php and mod_perl.
To use mod_apparmor with Apache, ensure that mod_apparmor is configured to be loaded into Apache, either via a2enmod, yast or manual
editing of the apache2(8)/httpd(8) configuration files, and restart Apache. Make sure that apparmor is also functioning.
Once mod_apparmor is loaded within Apache, all requests to Apache will cause mod_apparmor to attempt to change into a hat named by the URI
(e.g. /app/some.cgi). If no such hat is found, it will fall back to attempting to use the hat DEFAULT_URI; if that also does not exist, it
will fall back to using the global Apache profile. Most static web pages can simply make use of the DEFAULT_URI hat.
Additionally, before any requests come in to Apache, mod_apparmor will attempt to change hat into the HANDLING_UNTRUSTED_INPUT hat.
mod_apparmor will attempt to use this hat while Apache is doing the initial parsing of a given http request, before its given to a specific
handler (like mod_php) for processing.
Because defining hats for every URI/URL often becomes tedious, mod_apparmor provides the AAHatName and AADefaultHatName Apache
configuration options.
AAHatName
AAHatName allows you to specify a hat to be used for a given Apache <Directory>, <DirectoryMatch>, <Location> or <LocationMatch>
directive (see the Apache documenation for more details). Note that mod_apparmor behavior can become confused if <Directory*> and
<Location*> directives are intermingled and it is recommended to use one type of directive. If the hat specified by AAHatName does not
exist in the Apache profile, then it falls back to the behavior described above.
AADefaultHatName
AADefaultHatName allows you to specify a default hat to be used for virtual hosts and other Apache server directives, so that you can
have different defaults for different virtual hosts. This can be overridden by the AAHatName directive and is checked for only if there
isn't a matching AAHatName or hat named by the URI. If the AADefaultHatName hat does not exist, it falls back to the DEFAULT_URI hat if
it exists (as described above).
URI REQUEST SUMMARY
When profiling with mod_apparmor, it is helpful to keep the following order of operations in mind:
On each URI request, mod_apparmor will first aa_change_hat(2) into ^HANDLING_UNTRUSTED_INPUT, if it exists.
Then, after performing the initial parsing of the request, mod_apparmor will:
1. try to aa_change_hat(2) into a matching AAHatName hat if it exists and applies, otherwise it will
2. try to aa_change_hat(2) into the URI itself, otherwise it will
3. try to aa_change_hat(2) into an AADefaultHatName hat if it has been defined for the server/vhost, otherwise it will
4. try to aa_change_hat(2) into the DEFAULT_URI hat, if it exists, otherwise it will
5. fall back to the global Apache policy
BUGS
mod_apparmor() currently only supports apache2, and has only been tested with the prefork MPM configuration -- threaded configurations of
Apache may not work correctly.
There are likely other bugs lurking about; if you find any, please report them at <http://https://bugs.launchpad.net/apparmor/+filebug>.
SEE ALSO apparmor(7), subdomain.conf(5), apparmor_parser(8), aa_change_hat(2) and <http://wiki.apparmor.net>.
AppArmor 2.7.103 2012-06-28 MOD_APPARMOR(8)