archive-com.com » COM » C » CAPITALSAFETY.COM

Total: 175

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • mod_authnz_ldap - Apache HTTP Server

    (No additional info available in detailed archive for this subpage)
    Original URL path: /manual/mod/mod_authnz_ldap.html (2016-02-16)



  • mod_authz_dbm - Apache HTTP Server

    (No additional info available in detailed archive for this subpage)
    Original URL path: /manual/mod/mod_authz_dbm.html (2016-02-16)


  • mod_authz_owner - Apache HTTP Server

    (No additional info available in detailed archive for this subpage)
    Original URL path: /manual/mod/mod_authz_owner.html (2016-02-16)


  • Name-based Virtual Host Support - Apache HTTP Server
    make the server listen to that IP address See Setting which addresses and ports Apache uses for more details In addition any IP address specified here must be associated with a network interface on the server The next step is to create a VirtualHost block for each different host that you would like to serve The argument to the VirtualHost directive should be the same as the argument to the NameVirtualHost directive ie an IP address or for all addresses Inside each VirtualHost block you will need at minimum a ServerName directive to designate which host is served and a DocumentRoot directive to show where in the filesystem the content for that host lives Main host goes away If you are adding virtual hosts to an existing web server you must also create a VirtualHost block for the existing host The ServerName and DocumentRoot included in this virtual host should be the same as the global ServerName and DocumentRoot List this virtual host first in the configuration file so that it will act as the default host For example suppose that you are serving the domain www domain tld and you wish to add the virtual host www otherdomain tld which points at the same IP address Then you simply add the following to httpd conf NameVirtualHost 80 VirtualHost 80 ServerName www domain tld ServerAlias domain tld domain tld DocumentRoot www domain VirtualHost VirtualHost 80 ServerName www otherdomain tld DocumentRoot www otherdomain VirtualHost You can alternatively specify an explicit IP address in place of the in both the NameVirtualHost and VirtualHost directives For example you might want to do this in order to run some name based virtual hosts on one IP address and either IP based or another set of name based virtual hosts on another address Many servers want to be accessible by more than one name This is possible with the ServerAlias directive placed inside the VirtualHost section For example in the first VirtualHost block above the ServerAlias directive indicates that the listed names are other names which people can use to see that same web site ServerAlias domain tld domain tld then requests for all hosts in the domain tld domain will be served by the www domain tld virtual host The wildcard characters and can be used to match names Of course you can t just make up names and place them in ServerName or ServerAlias You must first have your DNS server properly configured to map those names to an IP address associated with your server Finally you can fine tune the configuration of the virtual hosts by placing other directives inside the VirtualHost containers Most directives can be placed in these containers and will then change the configuration only of the relevant virtual host To find out if a particular directive is allowed check the Context of the directive Configuration directives set in the main server context outside any VirtualHost container will be used only if they are not overridden by the virtual

    Original URL path: http://bc.capitalsafety.com/manual/vhosts/name-based.html (2016-02-16)
    Open archived version from archive

  • Issues Regarding DNS and Apache - Apache HTTP Server
    snippet that avoids both of these problems VirtualHost 10 0 0 1 ServerName www abc dom ServerAdmin webgirl abc dom DocumentRoot www abc VirtualHost Denial of Service There are at least two forms that denial of service can come in If you are running a version of Apache prior to version 1 2 then your server will not even boot if one of the two DNS lookups mentioned above fails for any of your virtual hosts In some cases this DNS lookup may not even be under your control for example if abc dom is one of your customers and they control their own DNS they can force your pre 1 2 server to fail while booting simply by deleting the www abc dom record Another form is far more insidious Consider this configuration snippet VirtualHost www abc dom ServerAdmin webgirl abc dom DocumentRoot www abc VirtualHost VirtualHost www def dom ServerAdmin webguy def dom DocumentRoot www def VirtualHost Suppose that you ve assigned 10 0 0 1 to www abc dom and 10 0 0 2 to www def dom Furthermore suppose that def dom has control of their own DNS With this config you have put def dom into a position where they can steal all traffic destined to abc dom To do so all they have to do is set www def dom to 10 0 0 1 Since they control their own DNS you can t stop them from pointing the www def dom record wherever they wish Requests coming in to 10 0 0 1 including all those where users typed in URLs of the form http www abc dom whatever will all be served by the def dom virtual host To better understand why this happens requires a more in depth discussion of how Apache matches up incoming requests with the virtual host that will serve it A rough document describing this is available The main server Address The addition of name based virtual host support in Apache 1 1 requires Apache to know the IP address es of the host that httpd is running on To get this address it uses either the global ServerName if present or calls the C function gethostname which should return the same as typing hostname at the command prompt Then it performs a DNS lookup on this address At present there is no way to avoid this lookup If you fear that this lookup might fail because your DNS server is down then you can insert the hostname in etc hosts where you probably already have it so that the machine can boot properly Then ensure that your machine is configured to use etc hosts in the event that DNS fails Depending on what OS you are using this might be accomplished by editing etc resolv conf or maybe etc nsswitch conf If your server doesn t have to perform DNS for any other reason then you might be able to get away with running Apache with

    Original URL path: http://bc.capitalsafety.com/manual/dns-caveats.html (2016-02-16)
    Open archived version from archive

  • Starting Apache - Apache HTTP Server
    controlled by the selected Multi Processing Module The recommended method of invoking the httpd executable is to use the apachectl control script This script sets certain environment variables that are necessary for httpd to function correctly under some operating systems and then invokes the httpd binary apachectl will pass through any command line arguments so any httpd options may also be used with apachectl You may also directly edit the apachectl script by changing the HTTPD variable near the top to specify the correct location of the httpd binary and any command line arguments that you wish to be always present The first thing that httpd does when it is invoked is to locate and read the configuration file httpd conf The location of this file is set at compile time but it is possible to specify its location at run time using the f command line option as in usr local apache2 bin apachectl f usr local apache2 conf httpd conf If all goes well during startup the server will detach from the terminal and the command prompt will return almost immediately This indicates that the server is up and running You can then use your browser to connect to the server and view the test page in the DocumentRoot directory and the local copy of the documentation linked from that page Errors During Start up If Apache suffers a fatal problem during startup it will write a message describing the problem either to the console or to the ErrorLog before exiting One of the most common error messages is Unable to bind to Port This message is usually caused by either Trying to start the server on a privileged port when not logged in as the root user or Trying to start the server when there is another

    Original URL path: http://bc.capitalsafety.com/manual/invoking.html (2016-02-16)
    Open archived version from archive

  • mod_proxy - Apache HTTP Server

    (No additional info available in detailed archive for this subpage)
    Original URL path: /manual/mod/mod_proxy.html (2016-02-16)


  • mod_info - Apache HTTP Server

    (No additional info available in detailed archive for this subpage)
    Original URL path: /manual/mod/mod_info.html (2016-02-16)




  •