archive-fr.com » FR » O » OBSPM.FR

Total: 155

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

Or switch to "Titles and links view".
  • Apache Virtual Host documentation - Apache HTTP Server
    have multiple names running on each IP address The fact that they are running on the same physical server is not apparent to the end user Apache was one of the first servers to support IP based virtual hosts right out of the box Versions 1 1 and later of Apache support both IP based and name based virtual hosts vhosts The latter variant of virtual hosts is sometimes also called host based or non IP virtual hosts Below is a list of documentation pages which explain all details of virtual host support in Apache version 1 3 and later Virtual Host Support Configuration directives See also mod vhost alias Name based virtual hosts IP based virtual hosts Virtual host examples File descriptor limits Mass virtual hosting Details of host matching Virtual Host Support Name based Virtual Hosts More than one web site per IP address IP based Virtual Hosts An IP address for each web site Virtual Host examples for common setups File Descriptor Limits or Too many log files Dynamically Configured Mass Virtual Hosting In Depth Discussion of Virtual Host Matching Configuration directives VirtualHost NameVirtualHost ServerName ServerAlias ServerPath If you are trying to debug your virtual host configuration

    Original URL path: http://ama09.obspm.fr/manual-2.0/vhosts/ (2015-11-16)
    Open archived version from archive


  • Authentication, Authorization and Access Control - Apache HTTP Server
    client to the browser unencrypted This method should therefore not be used for highly sensitive data Apache supports one other authentication method AuthType Digest This method is implemented by mod auth digest and is much more secure Only the most recent versions of clients are known to support Digest authentication The AuthName directive sets the Realm to be used in the authentication The realm serves two major functions First the client often presents this information to the user as part of the password dialog box Second it is used by the client to determine what password to send for a given authenticated area So for example once a client has authenticated in the Restricted Files area it will automatically retry the same password for any area on the same server that is marked with the Restricted Files Realm Therefore you can prevent a user from being prompted more than once for a password by letting multiple restricted areas share the same realm Of course for security reasons the client will always need to ask again for the password whenever the hostname of the server changes The AuthUserFile directive sets the path to the password file that we just created with htpasswd If you have a large number of users it can be quite slow to search through a plain text file to authenticate the user on each request Apache also has the ability to store user information in fast database files The mod auth dbm module provides the AuthDBMUserFile directive These files can be created and manipulated with the dbmmanage program Many other types of authentication options are available from third party modules in the Apache Modules Database Finally the Require directive provides the authorization part of the process by setting the user that is allowed to access this region of the server In the next section we discuss various ways to use the Require directive Letting more than one person in The directives above only let one person specifically someone with a username of rbowen into the directory In most cases you ll want to let more than one person in This is where the AuthGroupFile comes in If you want to let more than one person in you ll need to create a group file that associates group names with a list of users in that group The format of this file is pretty simple and you can create it with your favorite editor The contents of the file will look like this GroupName rbowen dpitts sungo rshersey That s just a list of the members of the group in a long line separated by spaces To add a user to your already existing password file type htpasswd usr local apache passwd password dpitts You ll get the same response as before but it will be appended to the existing file rather than creating a new file It s the c that makes it create a new password file Now you need to modify your htaccess file to

    Original URL path: http://ama09.obspm.fr/manual-2.0/howto/auth.html (2015-11-16)
    Open archived version from archive

  • Apache Tutorial: Dynamic Content with CGI - Apache HTTP Server
    but once you get that working you ll have a good chance of getting just about anything working But it s still not working There are four basic things that you may see in your browser when you try to access your CGI program from the web The output of your CGI program Great That means everything worked fine The source code of your CGI program or a POST Method Not Allowed message That means that you have not properly configured Apache to process your CGI program Reread the section on configuring Apache and try to find what you missed A message starting with Forbidden That means that there is a permissions problem Check the Apache error log and the section below on file permissions A message saying Internal Server Error If you check the Apache error log you will probably find that it says Premature end of script headers possibly along with an error message generated by your CGI program In this case you will want to check each of the below sections to see what might be preventing your CGI program from emitting the proper HTTP headers File permissions Remember that the server does not run as you That is when the server starts up it is running with the permissions of an unprivileged user usually nobody or www and so it will need extra permissions to execute files that are owned by you Usually the way to give a file sufficient permissions to be executed by nobody is to give everyone execute permission on the file chmod a x first pl Also if your program reads from or writes to any other files those files will need to have the correct permissions to permit this The exception to this is when the server is configured to use suexec This program allows CGI programs to be run under different user permissions depending on which virtual host or user home directory they are located in Suexec has very strict permission checking and any failure in that checking will result in your CGI programs failing with an Internal Server Error In this case you will need to check the suexec log file to see what specific security check is failing Path information When you run a program from your command line you have certain information that is passed to the shell without you thinking about it For example you have a path which tells the shell where it can look for files that you reference When a program runs through the web server as a CGI program it does not have that path Any programs that you invoke in your CGI program like sendmail for example will need to be specified by a full path so that the shell can find them when it attempts to execute your CGI program A common manifestation of this is the path to the script interpreter often perl indicated in the first line of your CGI program which will look something like usr bin

    Original URL path: http://ama09.obspm.fr/manual-2.0/howto/cgi.html (2015-11-16)
    Open archived version from archive

  • Apache Tutorial: .htaccess files - Apache HTTP Server
    every directory for htaccess files Thus permitting htaccess files causes a performance hit whether or not you actually even use them Also the htaccess file is loaded every time a document is requested Further note that Apache must look for htaccess files in all higher level directories in order to have a full complement of directives that it must apply See section on how directives are applied Thus if a file is requested out of a directory www htdocs example Apache must look for the following files htaccess www htaccess www htdocs htaccess www htdocs example htaccess And so for each file access out of that directory there are 4 additional file system accesses even if none of those files are present Note that this would only be the case if htaccess files were enabled for which is not usually the case The second consideration is one of security You are permitting users to modify server configuration which may result in changes over which you have no control Carefully consider whether you want to give your users this privilege Note also that giving users less privileges than they need will lead to additional technical support requests Make sure you clearly tell your users what level of privileges you have given them Specifying exactly what you have set AllowOverride to and pointing them to the relevant documentation will save yourself a lot of confusion later Note that it is completely equivalent to put a htaccess file in a directory www htdocs example containing a directive and to put that same directive in a Directory section Directory www htdocs example in your main server configuration htaccess file in www htdocs example Contents of htaccess file in www htdocs example AddType text example exm Section from your httpd conf file Directory www htdocs example AddType text example exm Directory However putting this configuration in your server configuration file will result in less of a performance hit as the configuration is loaded once when Apache starts rather than every time a file is requested The use of htaccess files can be disabled completely by setting the AllowOverride directive to none AllowOverride None How directives are applied The configuration directives found in a htaccess file are applied to the directory in which the htaccess file is found and to all subdirectories thereof However it is important to also remember that there may have been htaccess files in directories higher up Directives are applied in the order that they are found Therefore a htaccess file in a particular directory may override directives found in htaccess files found higher up in the directory tree And those in turn may have overridden directives found yet higher up or in the main server configuration file itself Example In the directory www htdocs example1 we have a htaccess file containing the following Options ExecCGI Note you must have AllowOverride Options in effect to permit the use of the Options directive in htaccess files In the directory www htdocs example1 example2

    Original URL path: http://ama09.obspm.fr/manual-2.0/howto/htaccess.html (2015-11-16)
    Open archived version from archive

  • Apache Tutorial: Introduction to Server Side Includes - Apache HTTP Server
    modify that formatting config timefmt A B d Y Today is echo var DATE LOCAL Modification date of the file This document last modified flastmod file index html This element is also subject to timefmt format configurations Including the results of a CGI program This is one of the more common uses of SSI to output the results of a CGI program such as everybody s favorite a hit counter include virtual cgi bin counter pl Additional examples Following are some specific examples of things you can do in your HTML documents with SSI When was this document modified Earlier we mentioned that you could use SSI to inform the user when the document was most recently modified However the actual method for doing that was left somewhat in question The following code placed in your HTML document will put such a time stamp on your page Of course you will have to have SSI correctly enabled as discussed above config timefmt A B d Y This file last modified flastmod file ssi shtml Of course you will need to replace the ssi shtml with the actual name of the file that you re referring to This can be inconvenient if you re just looking for a generic piece of code that you can paste into any file so you probably want to use the LAST MODIFIED variable instead config timefmt D This file last modified echo var LAST MODIFIED For more details on the timefmt format go to your favorite search site and look for strftime The syntax is the same Including a standard footer If you are managing any site that is more than a few pages you may find that making changes to all those pages can be a real pain particularly if you are trying to maintain some kind of standard look across all those pages Using an include file for a header and or a footer can reduce the burden of these updates You just have to make one footer file and then include it into each page with the include SSI command The include element can determine what file to include with either the file attribute or the virtual attribute The file attribute is a file path relative to the current directory That means that it cannot be an absolute file path starting with nor can it contain as part of that path The virtual attribute is probably more useful and should specify a URL relative to the document being served It can start with a but must be on the same server as the file being served include virtual footer html I ll frequently combine the last two things putting a LAST MODIFIED directive inside a footer file to be included SSI directives can be contained in the included file and includes can be nested that is the included file can include another file and so on What else can I config In addition to being able to config the time format you

    Original URL path: http://ama09.obspm.fr/manual-2.0/howto/ssi.html (2015-11-16)
    Open archived version from archive

  • Per-user web directories - Apache HTTP Server
    also Mapping URLs to the Filesystem Per user web directories Related Modules Related Directives mod userdir UserDir DirectoryMatch AllowOverride Setting the file path with UserDir The UserDir directive specifies a directory out of which per user content is loaded This directive may take several different forms If a path is given which does not start with a leading slash it is assumed to be a directory path relative to the home directory of the specified user Given this configuration UserDir public html the URL http example com rbowen file html will be translated to the file path home rbowen public html file html If a path is given starting with a slash a directory path will be constructed using that path plus the username specified Given this configuration UserDir var html the URL http example com rbowen file html will be translated to the file path var html rbowen file html If a path is provided which contains an asterisk a path is used in which the asterisk is replaced with the username Given this configuration UserDir var www docs the URL http example com rbowen file html will be translated to the file path var www rbowen docs file html Restricting what users are permitted to use this feature Using the syntax show in the UserDir documentation you can restrict what users are permitted to use this functionality UserDir enabled UserDir disabled root jro fish The configuration above will enable the feature for all users except for those listed in the disabled statement You can likewise disable the feature for all but a few users by using a configuration like the following UserDir disabled UserDir enabled rbowen krietz See UserDir documentation for additional examples Enabling a cgi directory for each user In order to give each user their own

    Original URL path: http://ama09.obspm.fr/manual-2.0/howto/public_html.html (2015-11-16)
    Open archived version from archive

  • Using Apache with Microsoft Windows - Apache HTTP Server
    method Apache uses to find the interpreter for the script is configurable using the ScriptInterpreterSource directive Since it is often difficult to manage files with names like htaccess in Windows you may find it useful to change the name of this per directory configuration file using the AccessFilename directive Any errors during Apache startup are logged into the Windows event log when running on Windows NT This mechanism acts as a backup for those situations where Apache cannot even access the normally used error log file You can view the Windows event log by using the Event Viewer application on Windows NT 4 0 and the Event Viewer MMC snap in on newer versions of Windows Note that there is no startup error logging on Windows 9x because no Windows event log exists on those operating systems Running Apache as a Service Apache can be run as a service on Windows NT There is some highly experimental support for similar behavior on Windows 9x You can install Apache as a service automatically during the installation If you chose to install for all users the installation will create an Apache service for you If you specify to install for yourself only you can manually register Apache as a service after the installation You have to be a member of the Administrators group for the service installation to succeed Apache comes with a utility called the Apache Service Monitor With it you can see and manage the state of all installed Apache services on any machine on your network To be able to manage an Apache service with the monitor you have to first install the service either automatically via the installation or manually You can install Apache as a Windows NT service as follows from the command prompt at the Apache bin subdirectory apache k install If you need to specify the name of the service you want to install use the following command You have to do this if you have several different service installations of Apache on your computer apache k install n MyServiceName If you need to have specifically named configuration files for different services you must use this apache k install n MyServiceName f c files my conf If you use the first command without any special parameters except k install the service will be called Apache2 and the configuration will be assumed to be conf httpd conf Removing an Apache service is easy Just use apache k uninstall The specific Apache service to be uninstalled can be specified by using apache k uninstall n MyServiceName Normal starting restarting and shutting down of an Apache service is usually done via the Apache Service Monitor by using commands like NET START Apache2 and NET STOP Apache2 or via normal Windows service management Before starting Apache as a service by any means you should test the service s configuration file by using apache n MyServiceName t You can control an Apache service by its command line switches too To start an installed Apache service you ll use this apache k start To stop an Apache service via the command line switches use this apache k stop or apache k shutdown You can also restart a running service and force it to reread its configuration file by using apache k restart By default all Apache services are registered to run as the system user the LocalSystem account The LocalSystem account has no privileges to your network via any Windows secured mechanism including the file system named pipes DCOM or secure RPC It has however wide privileges locally Never grant any network privileges to the LocalSystem account If you need Apache to be able to access network resources create a separate account for Apache as noted below You may want to create a separate account for running Apache service s Especially if you have to access network resources via Apache this is strongly recommended Create a normal domain user account and be sure to memorize its password Grant the newly created user a privilege of Log on as a service and Act as part of the operating system On Windows NT 4 0 these privileges are granted via User Manager for Domains but on Windows 2000 and XP you probably want to use Group Policy for propagating these settings You can also manually set these via the Local Security Policy MMC snap in Confirm that the created account is a member of the Users group Grant the account read and execute RX rights to all document and script folders htdocs and cgi bin for example Grant the account change RWXD rights to the Apache logs directory Grant the account read and execute RX rights to the Apache exe binary executable It is usually a good practice to grant the user the Apache service runs as read and execute RX access to the whole Apache2 directory except the logs subdirectory where the user has to have at least change RWXD rights If you allow the account to log in as a user and as a service then you can log on with that account and test that the account has the privileges to execute the scripts read the web pages and that you can start Apache in a console window If this works and you have followed the steps above Apache should execute as a service with no problems Error code 2186 is a good indication that you need to review the Log On As configuration for the service since Apache cannot access a required network resource Also pay close attention to the privileges of the user Apache is configured to run as When starting Apache as a service you may encounter an error message from the Windows Service Control Manager For example if you try to start Apache by using the Services applet in the Windows Control Panel you may get the following message Could not start the Apache2 service on COMPUTER Error 1067 The process terminated unexpectedly You will get

    Original URL path: http://ama09.obspm.fr/manual-2.0/platform/windows.html (2015-11-16)
    Open archived version from archive

  • Using Apache With Novell NetWare - Apache HTTP Server
    my conf apache f test test conf In these cases the proper ServerRoot should be set in the configuration file If you don t specify a configuration file name with f Apache will use the file name compiled into the server usually conf httpd conf Invoking Apache with the V switch will display this value labeled as SERVER CONFIG FILE Apache will then determine its ServerRoot by trying the following in this order A ServerRoot directive via a C switch The d switch on the command line Current working directory The server root compiled into the server The server root compiled into the server is usually sys apache2 invoking apache with the V switch will display this value labeled as HTTPD ROOT Apache 2 0 for NetWare includes a set of command line directives that can be used to modify or display information about the running instance of the web server These directives are only available while Apache is running Each of these directives must be preceded by the keyword APACHE2 RESTART Instructs Apache to terminate all running worker threads as they become idle reread the configuration file and restart each worker thread based on the new configuration VERSION Displays version information about the currently running instance of Apache MODULES Displays a list of loaded modules both built in and external DIRECTIVES Displays a list of all available directives SETTINGS Enables or disables the thread status display on the console When enabled the state of each running threads is displayed on the Apache console screen SHUTDOWN Terminates the running instance of the Apache web server HELP Describes each of the runtime directives By default these directives are issued against the instance of Apache running in the OS address space To issue a directive against a specific instance running in a protected address space include the p parameter along with the name of the address space For more information type apache2 Help on the command line Configuring Apache for NetWare Apache is configured by reading configuration files usually stored in the conf directory These are the same as files used to configure the Unix version but there are a few different directives for Apache on NetWare See the Apache documentation for all the available directives The main differences in Apache for NetWare are Because Apache for NetWare is multithreaded it does not use a separate process for each request as Apache does on some Unix implementations Instead there are only threads running a parent thread and multiple child or worker threads which handle the requests Therefore the process management directives are different MaxRequestsPerChild Like the Unix directive this controls how many requests a worker thread will serve before exiting The recommended default MaxRequestsPerChild 0 causes the thread to continue servicing request indefinitely It is recommended on NetWare unless there is some specific reason that this directive always remain set to 0 StartThreads This directive tells the server how many threads it should start initially The recommended default is StartThreads 50 MinSpareThreads

    Original URL path: http://ama09.obspm.fr/manual-2.0/platform/netware.html (2015-11-16)
    Open archived version from archive



  •