www.archive-dk-2012.com » DK » F » FLATBEAT

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

Or switch to "Titles and links view".

    Archived pages: 174 . Archive date: 2012-11.

  • Title: Test Page for the Apache Web Server on Red Hat Linux
    Descriptive info: .. Test Page.. Dette er en testsideThis page is used to test the proper operation of the Apache Web server after it has been installed.. If you can read this page, it means that the Apache Web server installed at this site is working properly.. If you are the administrator of this website:.. You may now add content to this directory, and replace this page.. Note that until you do so, people visiting your website will see this page, and not your content.. If you have upgraded from Red Hat Linux 6.. 2 and earlier, then you are seeing this page because the default.. DocumentRoot.. set in.. /etc/httpd/conf/httpd.. conf.. has changed.. Any subdirectories which existed under.. /home/httpd.. should now be moved to.. /var/www.. Alternatively, the contents of.. can be moved to..  ...   to let the administrators of this website know that you've seen this page instead of the page you expected, you should send them e-mail.. In general, mail sent to the name "webmaster" and directed to the website's domain should reach the appropriate person.. For example, if you experienced problems while visiting www.. example.. com, you should send e-mail to "webmaster@example.. com".. The Apache.. documentation.. has been included with this distribution.. For documentation and information on Red Hat Linux, please visit the.. Red Hat, Inc.. website.. The manual for Red Hat Linux is available.. here.. You are free to use the image below on an Apache-powered Web server.. Thanks for using Apache!.. You are free to use the image below on a Red Hat Linux-powered Web server.. Thanks for using Red Hat Linux!..

    Original link path: /
    Open archive

  • Title: core - Apache HTTP Server
    Descriptive info: Modules.. |.. Directives.. FAQ.. Glossary.. Sitemap.. Apache HTTP Server Version 2.. 2.. Apache.. HTTP Server.. Documentation.. Version 2.. Apache Core Features.. Available Languages:.. de.. en.. ja.. Description:.. Core Apache HTTP Server features that are always available.. Status:.. Core.. AcceptFilter.. AcceptPathInfo.. AccessFileName.. AddDefaultCharset.. AddOutputFilterByType.. AllowEncodedSlashes.. AllowOverride.. AuthName.. AuthType.. CGIMapExtension.. ContentDigest.. DefaultType.. Directory.. DirectoryMatch.. EnableMMAP.. EnableSendfile.. ErrorDocument.. ErrorLog.. FileETag.. Files.. FilesMatch.. ForceType.. HostnameLookups.. IfDefine.. IfModule.. Include.. KeepAlive.. KeepAliveTimeout.. Limit.. LimitExcept.. LimitInternalRecursion.. LimitRequestBody.. LimitRequestFields.. LimitRequestFieldSize.. LimitRequestLine.. LimitXMLRequestBody.. Location.. LocationMatch.. LogLevel.. MaxKeepAliveRequests.. NameVirtualHost.. Options.. Require.. RLimitCPU.. RLimitMEM.. RLimitNPROC.. Satisfy.. ScriptInterpreterSource.. ServerAdmin.. ServerAlias.. ServerName.. ServerPath.. ServerRoot.. ServerSignature.. ServerTokens.. SetHandler.. SetInputFilter.. SetOutputFilter.. TimeOut.. TraceEnable.. UseCanonicalName.. UseCanonicalPhysicalPort.. VirtualHost.. Directive.. Configures optimizations for a Protocol's Listener Sockets.. Syntax:.. AcceptFilter.. protocol.. accept_filter.. Context:.. server config.. Module:.. core.. Compatibility:.. Available in Apache 2.. 1.. 5 and later.. This directive enables operating system specific optimizations for a listening socket by the Protocol type.. The basic premise is for the kernel to not send a socket to the server process until either data is received or an entire HTTP Request is buffered.. Only.. FreeBSD's Accept Filters.. and Linux's more primitive.. TCP_DEFER_ACCEPT.. are currently supported.. The default values on FreeBSD are:.. AcceptFilter http httpready.. AcceptFilter https dataready.. The.. httpready.. accept filter buffers entire HTTP requests at the kernel level.. Once an entire request is recieved, the kernel then sends it to the server.. See the.. accf_http(9).. man page for more details.. Since HTTPS requests are encrypted only the.. accf_data(9).. filter is used.. The default values on Linux are:.. AcceptFilter http data.. AcceptFilter https data.. Linux's.. does not support buffering http requests.. Any value besides.. none.. will enable.. on that listener.. For more details see the Linux.. tcp(7).. man page.. Using.. for an argument will disable any accept filters for that protocol.. This is useful for protocols that require a server send data first, such as.. nntp.. :.. AcceptFilter nttp none.. Resources accept trailing pathname information.. AcceptPathInfo On|Off|Default.. Default:.. AcceptPathInfo Default.. server config, virtual host, directory,.. htaccess.. Override:.. FileInfo.. 0.. 30 and later.. This directive controls whether requests that contain trailing pathname information that follows an actual filename (or non-existent file in an existing directory) will be accepted or rejected.. The trailing pathname information can be made available to scripts in the.. PATH_INFO.. environment variable.. For example, assume the location.. /test/.. points to a directory that contains only the single file.. html.. Then requests for.. /test/here.. html/more.. and.. /test/nothere.. both collect.. /more.. as.. The three possible arguments for the.. directive are:.. Off.. A request will only be accepted if it maps to a literal path that exists.. Therefore a request with trailing pathname information after the true filename such as.. in the above example will return a 404 NOT FOUND error.. On.. A request will be accepted if a leading path component maps to a file that exists.. The above example.. will be accepted if.. maps to a valid file.. Default.. The treatment of requests with trailing pathname information is determined by the.. handler.. responsible for the request.. The core handler for normal files defaults to rejecting.. requests.. Handlers that serve scripts, such as.. cgi-script.. isapi-handler.. , generally accept.. by default.. The primary purpose of the.. directive is to allow you to override the handler's choice of accepting or rejecting.. This override is required, for example, when you use a.. filter.. , such as.. INCLUDES.. , to generate content based on.. The core handler would usually reject the request, so you can use the following configuration to enable such a script:.. Files "mypaths.. shtml".. Options +Includes.. SetOutputFilter INCLUDES.. AcceptPathInfo On.. /Files.. Name of the distributed configuration file.. AccessFileName.. filename.. [.. ].. server config, virtual host.. While processing a request the server looks for the first existing configuration file from this list of names in every directory of the path to the document, if distributed configuration files are.. enabled for that directory.. For example:.. acl.. before returning the document.. /usr/local/web/index.. , the server will read.. /.. acl.. ,.. /usr/.. /usr/local/.. /usr/local/web/.. for directives, unless they have been disabled with.. Directory /.. AllowOverride None.. /Directory.. See also.. Configuration Files.. htaccess Files.. Default charset parameter to be added when a response content-type is.. text/plain.. or.. text/html.. AddDefaultCharset On|Off|.. charset.. AddDefaultCharset Off.. This directive specifies a default value for the media type charset parameter (the name of a character encoding) to be added to a response if and only if the response's content-type is either.. This should override any charset specified in the body of the response via a.. META.. element, though the exact behavior is often dependent on the user's client configuration.. A setting of.. disables this functionality.. AddDefaultCharset On.. enables a default charset of.. iso-8859-1.. Any other value is assumed to be the.. to be used, which should be one of the.. IANA registered charset values.. for use in MIME media types.. AddDefaultCharset utf-8.. should only be used when all of the text resources to which it applies are known to be in that character encoding and it is too inconvenient to label their charset individually.. One such example is to add the charset parameter to resources containing generated content, such as legacy CGI scripts, that might be vulnerable to cross-site scripting attacks due to user-provided data being included in the output.. Note, however, that a better solution is to just fix (or delete) those scripts, since setting a default charset does not protect users that have enabled the "auto-detect character encoding" feature on their browser.. AddCharset.. assigns an output filter to a particular MIME-type.. AddOutputFilterByType.. [;.. ].. MIME-type.. 33 and later; deprecated in Apache 2.. 1 and later.. This directive activates a particular output.. for a request depending on the response.. Because of certain problems discussed below, this directive is deprecated.. The same functionality is available using.. mod_filter.. The following example uses the.. DEFLATE.. filter, which is provided by.. mod_deflate.. It will compress all output (either static or dynamic) which is labeled as.. before it is sent to the client.. AddOutputFilterByType DEFLATE text/html text/plain.. If you want the content to be processed by more than one filter, their names have to be separated by semicolons.. It's also possible to use one.. directive for each of these filters.. The configuration below causes all script output labeled as.. to be processed at first by the.. filter and then by the.. Location /cgi-bin/.. Options Includes.. AddOutputFilterByType INCLUDES;DEFLATE text/html.. /Location.. Note.. Enabling filters with.. may fail partially or completely in some cases.. For example, no filters are applied if the.. could not be determined and falls back to the.. setting, even if the.. is the same.. However, if you want to make sure, that the filters will be applied, assign the content type to a resource explicitly, for example with.. AddType.. Setting the content type within a (non-nph) CGI script is also safe.. The by-type output filters are never applied on proxy requests.. AddOutputFilter.. filters.. Determines whether encoded path separators in URLs are allowed to be passed through.. AllowEncodedSlashes On|Off.. AllowEncodedSlashes Off.. 46 and later.. directive allows URLs which contain encoded path separators (.. %2F.. for.. and additionally.. %5C.. \.. on according systems) to be used.. Normally such URLs are refused with a 404 (Not found) error.. Turning.. is mostly useful when used in conjunction with.. Allowing encoded slashes does.. not.. imply.. decoding.. Occurrences of.. (.. only.. on according systems) will be left as such in the otherwise decoded URL string.. Types of directives that are allowed in.. files.. AllowOverride All|None|.. directive-type.. AllowOverride All.. directory.. When the server finds an.. file (as specified by.. ) it needs to know which directives declared in that file can override earlier configuration directives.. Only available in Directory sections.. is valid only in.. sections specified without regular expressions, not in.. sections.. When this directive is set to.. None.. , then.. files are completely ignored.. In this case, the server will not even attempt to read.. files in the filesystem.. All.. , then any directive which has the.. htaccess.. Context.. is allowed in.. can be one of the following groupings of directives.. AuthConfig.. Allow use of the authorization directives (.. AuthDBMGroupFile.. AuthDBMUserFile.. AuthGroupFile.. AuthUserFile.. etc.. ).. Allow use of the directives controlling document types (.. LanguagePriority.. , and.. mod_mime.. Add* and Remove* directives,.. ), document meta data (.. Header.. RequestHeader.. SetEnvIf.. SetEnvIfNoCase.. BrowserMatch.. CookieExpires.. CookieDomain.. CookieStyle.. CookieTracking.. CookieName.. ),.. mod_rewrite.. directives.. RewriteEngine.. RewriteOptions.. RewriteBase.. RewriteCond.. RewriteRule.. ) and.. Action.. from.. mod_actions.. Indexes.. Allow use of the directives controlling directory indexing (.. AddDescription.. AddIcon.. AddIconByEncoding.. AddIconByType.. DefaultIcon.. DirectoryIndex.. FancyIndexing.. HeaderName.. IndexIgnore.. IndexOptions.. ReadmeName.. Limit.. Allow use of the directives controlling host access (.. Allow.. Deny.. Order.. Options[=.. Option.. ,.. ].. Allow use of the directives controlling specific directory features (.. XBitHack.. An equal sign may be given followed by a comma (but no spaces) separated lists of options that may be set using the.. command.. Example:.. AllowOverride AuthConfig Indexes.. In the example above all directives that are neither in the group.. nor.. cause an internal server error.. Authorization realm for use in HTTP authentication.. AuthName.. auth-domain.. directory,.. This directive sets the name of the authorization realm for a directory.. This realm is given to the client so that the user knows which username and password to send.. takes a single argument; if the realm name contains spaces, it must be enclosed in quotation marks.. It must be accompanied by.. directives, and directives such as.. to work.. AuthName "Top Secret".. The string provided for the.. is what will appear in the password dialog provided by most browsers.. Authentication, Authorization, and Access Control.. Type of user authentication.. AuthType Basic|Digest.. This directive selects the type of user authentication for a directory.. The authentication types available are.. Basic.. (implemented by.. mod_auth_basic.. Digest.. mod_auth_digest.. To implement authentication, you must also use the.. directives.. In addition, the server must have an authentication-provider module such as.. mod_authn_file.. and an authorization module such as.. mod_authz_user.. Technique for locating the interpreter for CGI scripts.. CGIMapExtension.. cgi-path.. extension.. NetWare only.. This directive is used to control how Apache finds the interpreter used to run CGI scripts.. For example, setting.. CGIMapExtension sys:\foo.. nlm.. foo.. will cause all CGI script files with a.. extension to be passed to the FOO interpreter.. Enables the generation of.. Content-MD5.. HTTP Response headers.. ContentDigest On|Off.. ContentDigest Off.. This directive enables the generation of.. headers as defined in RFC1864 respectively RFC2068.. MD5 is an algorithm for computing a "message digest" (sometimes called "fingerprint") of arbitrary-length data, with a high degree of confidence that any alterations in the data will be reflected in alterations in the message digest.. header provides an end-to-end message integrity check (MIC) of the entity-body.. A proxy or client may check this header for detecting accidental modification of the entity-body in transit.. Example header:.. Content-MD5: AuLb7Dp1rqtRtxz2m9kRpA==.. Note that this can cause performance problems on your server since the message digest is computed on every request (the values are not cached).. is only sent for documents served by the.. , and not by any module.. For example, SSI documents, output from CGI scripts, and byte range responses do not have this header.. MIME content-type that will be sent if the server cannot determine a type in any other way.. DefaultType.. DefaultType text/plain.. There will be times when the server is asked to provide a document whose type cannot be determined by its.. MIME types.. mappings.. The server must inform the client of the content-type of the document, so in the event of an unknown type it uses the.. DefaultType image/gif.. would be appropriate for a directory which contained many GIF images with filenames missing the.. gif.. extension.. Note that unlike.. , this directive only provides the default mime-type.. All other mime-type definitions, including filename extensions, that might identify the media type will override this default.. Enclose a group of directives that apply only to the named file-system directory and sub-directories.. directory-path.. are used to enclose a group of directives that will apply only to the named directory and sub-directories of that directory.. Any directive that is allowed in a directory context may be used.. Directory-path.. is either the full path to a directory, or a wild-card string using Unix shell-style matching.. In a wild-card string,.. ?.. matches any single character, and.. *.. matches any sequences of characters.. You may also use.. [].. character ranges.. None of the wildcards match a `/' character, so.. Directory /*/public_html.. will not match.. /home/user/public_html.. , but.. Directory /home/*/public_html.. will match.. Directory /usr/local/httpd/htdocs.. Options Indexes FollowSymLinks.. Be careful with the.. arguments: They have to literally match the filesystem path which Apache uses to access the files.. Directives applied to a particular.. will not apply to files accessed from that same directory via a different path, such as via different symbolic links.. Regular expressions.. can also be used, with the addition of the.. ~.. character.. Directory ~ "^/www/.. */[0-9]{3}".. would match directories in.. /www/.. that consisted of three numbers.. If multiple (non-regular expression).. sections match the directory (or one of its parents) containing a document, then the directives are applied in the order of shortest match first, interspersed with the directives from the.. For example, with.. Directory /home/.. AllowOverride FileInfo.. for access to the document.. /home/web/dir/doc.. the steps are:.. Apply directive.. (disabling.. files).. (for directory.. /home.. Apply any.. directives in.. /home/.. /home/web/.. /home/web/dir/.. in that order.. Regular expressions are not considered until after all of the normal sections have been applied.. Then all of the regular expressions are tested in the order they appeared in the configuration file.. Directory ~ abc$.. #.. directives here.. the regular expression section won't be considered until after all normal.. s and.. files have been applied.. Then the regular expression will match on.. /home/abc/public_html/abc.. and the corresponding.. will be applied.. Note that the default Apache access for.. is.. Allow from All.. This means that Apache will serve any file mapped from an URL.. It is recommended that you change this with a block such as.. Order Deny,Allow.. Deny from All.. and then override this for directories you.. want.. accessible.. Security Tips.. page for more details.. The directory sections occur in the.. httpd.. file.. directives cannot nest, and cannot appear in a.. section.. How Directory , Location and Files sections work.. for an explanation of how these different sections are combined when a request is received.. Enclose directives that apply to file-system directories matching a regular expression and their subdirectories.. regex.. /DirectoryMatch.. are used to enclose a group of directives which will apply only to the named directory and sub-directories of that directory, the same as.. However, it takes as an argument a.. regular expression.. DirectoryMatch "^/www/(.. +/)?[0-9]{3}".. for a description of how regular expressions are mixed in with normal.. s.. Directory that forms the main document tree visible from the web.. DocumentRoot.. DocumentRoot /usr/local/apache/htdocs.. This directive sets the directory from which.. will serve files.. Unless matched by a directive like.. Alias.. , the server appends the path from the requested URL to the document root to make the path to the document.. DocumentRoot /usr/web.. then an access to.. http://www.. my.. host.. com/index.. refers to.. /usr/web/index.. If the.. is not absolute then it is assumed to be relative to the.. should be specified without a trailing slash.. Mapping URLs to Filesystem Location.. Use memory-mapping to read files during delivery.. EnableMMAP On|Off.. EnableMMAP On.. This directive controls whether the.. may use memory-mapping if it needs to read the contents of a file during delivery.. By default, when the handling of a request requires access to the data within a file -- for example, when delivering a server-parsed file using.. mod_include.. -- Apache memory-maps the file if the OS supports it.. This memory-mapping sometimes yields a performance improvement.. But in some environments, it is better to disable the memory-mapping to prevent operational problems:.. On some multiprocessor systems, memory-mapping can reduce the performance of the.. With an NFS-mounted.. , the.. may crash due to a segmentation fault if a file is deleted or truncated while the.. has it memory-mapped.. For server configurations that are vulnerable to these problems, you should disable memory-mapping of delivered files by specifying:.. EnableMMAP Off.. For NFS mounted files, this feature may be disabled explicitly for the offending files by specifying:.. Directory "/path-to-nfs-files".. Use the kernel sendfile support to deliver files to the client.. EnableSendfile On|Off.. EnableSendfile On.. Available in version 2.. 44 and later.. This directive controls whether.. may use the sendfile support from the kernel to transmit file contents to the client.. By default, when the handling of a request requires no access to the data within a file -- for example, when delivering a static file -- Apache uses sendfile to deliver the file contents without ever reading the file if the OS supports it.. This sendfile mechanism avoids separate read and send operations, and buffer allocations.. But on some platforms or within some filesystems, it is better to disable this feature to avoid operational problems:.. Some platforms may have broken sendfile support that the build system did not detect, especially if the binaries were built on another box and moved to such a machine with broken sendfile support.. On Linux the use of sendfile triggers TCP-checksum offloading bugs on certain networking cards when using IPv6.. On Linux on Itanium, sendfile may be unable to handle files over 2GB in size.. With a network-mounted.. (e.. g.. , NFS or SMB), the kernel may be unable to serve the network file through its own cache.. For server configurations that are vulnerable to these problems, you should disable this feature by specifying:.. EnableSendfile Off.. For NFS or SMB mounted files, this feature may be disabled explicitly for the offending files by specifying:.. What the server will return to the client in case of an error.. ErrorDocument.. error-code.. document.. Quoting syntax for text messages is different in Apache 2.. In the event of a problem or error, Apache can be configured to do one of four things,.. output a simple hardcoded error message.. output a customized message.. redirect to a local.. URL-path.. to handle the problem/error.. redirect to an external.. URL.. The first option is the default, while options 2-4 are configured using the.. directive, which is followed by the HTTP response code and a URL or a message.. Apache will sometimes offer additional information regarding the problem/error.. URLs can begin with a slash (/) for local web-paths (relative to the.. ), or be a full URL which the client can resolve.. Alternatively, a message can be provided to be displayed by the browser.. Examples:.. ErrorDocument 500 http://foo.. com/cgi-bin/tester.. ErrorDocument 404 /cgi-bin/bad_urls.. pl.. ErrorDocument 401 /subscription_info.. ErrorDocument 403 "Sorry can't allow you access today".. Additionally, the special value.. default.. can be used to specify Apache's simple hardcoded message.. While not required under normal circumstances,.. will restore Apache's simple hardcoded message for configurations that would otherwise inherit an existing.. Directory /web/docs.. ErrorDocument 404 default.. Note that when you specify an.. that points to a remote URL (ie.. anything with a method such as.. http.. in front of it), Apache will send a redirect to the client to tell it where to find the document, even if the document ends up being on the same server.. This has several implications, the most important being that the client will not receive the original error status code, but instead will receive a redirect status code.. This in turn can confuse web robots and other clients which try to determine if a URL is valid using the status code.. In addition, if you use a remote URL in an.. ErrorDocument 401.. , the client will not know to prompt the user for a password since it will not receive the 401 status code.. Therefore,.. if you use an.. directive then it must refer to a local document.. Microsoft Internet Explorer (MSIE) will by default ignore server-generated error messages when they are "too small" and substitute its own "friendly" error messages.. The size threshold varies depending on the type of error, but in general, if you make your error document greater than 512 bytes, then MSIE will show the server-generated error rather than masking it.. More information is available in Microsoft Knowledge Base article.. Q294807.. Although most error  ...   [2001:db8::a00:20ff:fea7:ccea]:8080.. To receive requests on all interfaces, you can use an argument of.. NameVirtualHost *.. Argument to.. Note that the argument to the.. directive must exactly match the argument to the.. NameVirtualHost 1.. 4.. VirtualHost 1.. 4.. /VirtualHost.. Virtual Hosts documentation.. Configures what features are available in a particular directory.. Options [+|-].. option.. [[+|-].. Options All.. directive controls which server features are available in a particular directory.. can be set to.. , in which case none of the extra features are enabled, or one or more of the following:.. All options except for.. MultiViews.. This is the default setting.. ExecCGI.. Execution of CGI scripts using.. mod_cgi.. is permitted.. FollowSymLinks.. The server will follow symbolic links in this directory.. Even though the server follows the symlink it does.. change the pathname used to match against.. Note also, that this option.. gets ignored.. if set inside a.. Includes.. Server-side includes provided by.. are permitted.. IncludesNOEXEC.. Server-side includes are permitted, but the.. #exec cmd.. #exec cgi.. are disabled.. It is still possible to.. #include virtual.. CGI scripts from.. ScriptAlias.. ed directories.. If a URL which maps to a directory is requested, and there is no.. e.. index.. ) in that directory, then.. mod_autoindex.. will return a formatted listing of the directory.. Content negotiated.. "MultiViews" are allowed using.. mod_negotiation.. SymLinksIfOwnerMatch.. The server will only follow symbolic links for which the target file or directory is owned by the same user id as the link.. This option gets ignored if set inside a.. Normally, if multiple.. could apply to a directory, then the most specific one is used and others are ignored; the options are not merged.. (See.. how sections are merged.. ) However if.. the options on the.. directive are preceded by a.. symbol, the options are merged.. Any options preceded by a.. are added to the options currently in force, and any options preceded by a.. are removed from the options currently in force.. For example, without any.. symbols:.. Directory /web/docs/spec.. then only.. will be set for the.. /web/docs/spec.. However if the second.. directive uses the.. Options +Includes -Indexes.. then the options.. are set for the.. -IncludesNOEXEC.. -Includes.. disables server-side includes completely regardless of the previous setting.. The default in the absence of any other settings is.. Selects which authenticated users can access a resource.. Require.. entity-name.. This directive selects which authenticated users can access a resource.. The restrictions are processed by authorization modules.. Some of the allowed syntaxes provided by.. mod_authz_groupfile.. are:.. Require user.. userid.. Only the named users can access the resource.. Require group.. group-name.. Only users in the named groups can access the resource.. All valid users can access the resource.. Other authorization modules that implement require options include.. mod_authnz_ldap.. mod_authz_dbm.. mod_authz_owner.. must be accompanied by.. (to define users and groups) in order to work correctly.. AuthType Basic.. AuthName "Restricted Resource".. AuthUserFile /web/users.. AuthGroupFile /web/groups.. Require group admin.. Access controls which are applied in this way are effective for.. methods.. This is what is normally desired.. If you wish to apply access controls only to specific methods, while leaving other methods unprotected, then place the.. statement into a.. is used together with the.. directives, then the interaction of these restrictions is controlled by the.. Removing controls in subdirectories.. The following example shows how to use the.. directive to disable access controls in a subdirectory of a protected directory.. This technique should be used with caution, because it will also disable any access controls imposed by.. Directory /path/to/protected/.. Require user david.. Directory /path/to/protected/unprotected.. # All access controls and authentication are disabled.. # in this directory.. Satisfy Any.. Allow from all.. Limits the CPU consumption of processes launched by Apache children.. RLimitCPU.. |max [.. |max].. Unset; uses operating system defaults.. Takes 1 or 2 parameters.. The first parameter sets the soft resource limit for all processes and the second parameter sets the maximum resource limit.. Either parameter can be a number, or.. max.. to indicate to the server that the limit should be set to the maximum allowed by the operating system configuration.. Raising the maximum resource limit requires that the server is running as.. root.. , or in the initial startup phase.. This applies to processes forked off from Apache children servicing requests, not the Apache children themselves.. This includes CGI scripts and SSI exec commands, but not any processes forked off from the Apache parent such as piped logs.. CPU resource limits are expressed in seconds per process.. Limits the memory consumption of processes launched by Apache children.. RLimitMEM.. Memory resource limits are expressed in bytes per process.. Limits the number of processes that can be launched by processes launched by Apache children.. RLimitNPROC.. Process limits control the number of processes per user.. If CGI processes are.. running under user ids other than the web server user id, this directive will limit the number of processes that the server itself can create.. Evidence of this situation will be indicated by.. cannot fork.. messages in the.. error_log.. Interaction between host-level access control and user authentication.. Satisfy Any|All.. Satisfy All.. Influenced by.. in version 2.. 51 and later.. Access policy if both.. used.. The parameter can be either.. Any.. This directive is only useful if access to a particular area is being restricted by both username/password.. and.. client host address.. In this case the default behavior (.. ) is to require that the client passes the address access restriction.. enters a valid username and password.. option the client will be granted access if they either pass the host restriction or enter a valid username and password.. This can be used to password restrict an area, but to let clients from particular addresses in without prompting for a password.. For example, if you wanted to let people on your network have unrestricted access to a portion of your website, but require that people outside of your network provide a password, you could use a configuration similar to the following:.. Allow from 192.. 168.. Satisfy Any.. Since version 2.. 51.. directives can be restricted to particular methods by.. ScriptInterpreterSource Registry|Registry-Strict|Script.. ScriptInterpreterSource Script.. Win32 only; option.. Registry-Strict.. is available in Apache 2.. 0 and later.. The default setting is.. Script.. This causes Apache to use the interpreter pointed to by the shebang line (first line, starting with.. #!.. ) in the script.. On Win32 systems this line usually looks like:.. #!C:/Perl/bin/perl.. exe.. or, if.. perl.. is in the.. PATH.. , simply:.. #!perl.. ScriptInterpreterSource Registry.. will cause the Windows Registry tree.. HKEY_CLASSES_ROOT.. to be searched using the script file extension (e.. ,.. ) as a search key.. The command defined by the registry subkey.. Shell\ExecCGI\Command.. or, if it does not exist, by the subkey.. Shell\Open\Command.. is used to open the script file.. If the registry keys cannot be found, Apache falls back to the behavior of the.. Security.. Be careful when using.. with.. 'ed directories, because Apache will try to execute.. every.. file within this directory.. Registry.. setting may cause undesired program calls on files which are typically not executed.. For example, the default open command on.. htm.. files on most Windows systems will execute Microsoft Internet Explorer, so any HTTP request for an.. file existing within the script directory would start the browser in the background on the server.. This is a good way to crash your system within a minute or so.. The option.. which is new in Apache 2.. 0 does the same thing as.. but uses only the subkey.. key is not a common one.. It must be configured manually in the windows registry and hence prevents accidental program calls on your system.. Email address that the server includes in error messages sent to the client.. ServerAdmin.. email-address.. sets the contact address that the server includes in any error messages it returns to the client.. doesn't recognize the supplied argument as an URL, it assumes, that it's an.. and prepends it with.. mailto:.. in hyperlink targets.. However, it's recommended to actually use an email address, since there are a lot of CGI scripts that make that assumption.. If you want to use an URL, it should point to another server under your control.. Otherwise users may not be able to contact you in case of errors.. It may be worth setting up a dedicated address for this, e.. ServerAdmin www-admin@foo.. com.. as users do not always mention that they are talking about the server!.. Alternate names for a host used when matching requests to name-virtual hosts.. ServerAlias.. hostname.. virtual host.. directive sets the alternate names for a host, for use with.. VirtualHost *.. ServerName server.. domain.. ServerAlias server server2.. com server2.. Apache Virtual Host documentation.. Hostname and port that the server uses to identify itself.. ServerName [.. scheme.. ://].. fully-qualified-domain-name.. In version 2.. 0, this directive supersedes the functionality of the.. Port.. directive from version 1.. directive sets the request scheme, hostname and port that the server uses to identify itself.. This is used when creating redirection URLs.. For example, if the name of the machine hosting the web server is.. simple.. , but the machine also has the DNS alias.. www.. and you wish the web server to be so identified, the following directive should be used:.. ServerName www.. com:80.. If no.. is specified, then the server attempts to deduce the hostname by performing a reverse lookup on the IP address.. If no port is specified in the.. , then the server will use the port from the incoming request.. For optimal reliability and predictability, you should specify an explicit hostname and port using the.. If you are using.. inside a.. section specifies what hostname must appear in the request's.. Host:.. header to match this virtual host.. Sometimes, the server runs behind a device that processes SSL, such as a reverse proxy, load balancer or SSL offload appliance.. When this is the case, specify the.. https://.. scheme and the port number to which the clients connect in the.. directive to make sure that the server generates the correct self-referential URLs.. See the description of the.. directives for settings which determine whether self-referential URLs (e.. , by the.. module) will refer to the specified port, or to the port number given in the client's request.. Issues Regarding DNS and Apache.. Apache virtual host documentation.. Legacy URL pathname for a name-based virtual host that is accessed by an incompatible browser.. ServerPath.. directive sets the legacy URL pathname for a host, for use with.. Base directory for the server installation.. ServerRoot.. ServerRoot /usr/local/apache.. directive sets the directory in which the server lives.. Typically it will contain the subdirectories.. conf/.. logs/.. Relative paths in other configuration directives (such as.. , for example) are taken as relative to this directory.. ServerRoot /home/httpd.. the.. -d.. option to.. the security tips.. for information on how to properly set permissions on the.. Configures the footer on server-generated documents.. ServerSignature On|Off|EMail.. ServerSignature Off.. directive allows the configuration of a trailing footer line under server-generated documents (error messages,.. mod_proxy.. ftp directory listings,.. mod_info.. output,.. The reason why you would want to enable such a footer line is that in a chain of proxies, the user often has no possibility to tell which of the chained servers actually produced a returned error message.. setting, which is the default, suppresses the footer line (and is therefore compatible with the behavior of Apache-1.. 2 and below).. setting simply adds a line with the server version number and.. of the serving virtual host, and the.. EMail.. setting additionally creates a "mailto:" reference to the.. of the referenced document.. After version 2.. 44, the details of the server version number presented are controlled by the.. Configures the.. Server.. HTTP response header.. ServerTokens Major|Minor|Min[imal]|Prod[uctOnly]|OS|Full.. ServerTokens Full.. response header field which is sent back to clients includes a description of the generic OS-type of the server as well as information about compiled-in modules.. ServerTokens Prod[uctOnly].. Server sends (.. ):.. Server: Apache.. ServerTokens Major.. Server: Apache/2.. ServerTokens Minor.. ServerTokens Min[imal].. 41.. ServerTokens OS.. 41 (Unix).. (or not specified).. 41 (Unix) PHP/4.. 2 MyMod/1.. This setting applies to the entire server, and cannot be enabled or disabled on a virtualhost-by-virtualhost basis.. 44, this directive also controls the information presented by the.. Forces all matching files to be processed by a handler.. SetHandler.. handler-name.. Moved into the core in Apache 2.. section, this directive forces all matching files to be parsed through the.. given by.. For example, if you had a directory you wanted to be parsed entirely as imagemap rule files, regardless of extension, you might put the following into an.. file in that directory:.. SetHandler imap-file.. Another example: if you wanted to have the server display a status report whenever a URL of.. http://servername/status.. was called, you might put the following into.. You can override an earlier defined.. directive by using the value.. AddHandler.. Sets the filters that will process client requests and POST input.. SetInputFilter.. directive sets the filter or filters which will process client requests and POST input when they are received by the server.. This is in addition to any filters defined elsewhere, including the.. AddInputFilter.. If more than one filter is specified, they must be separated by semicolons in the order in which they should process the content.. Filters.. Sets the filters that will process responses from the server.. SetOutputFilter.. directive sets the filters which will process responses from the server before they are sent to the client.. For example, the following configuration will process all files in the.. /www/data/.. directory for server-side includes.. Directory /www/data/.. Amount of time the server will wait for certain events before failing a request.. TimeOut.. TimeOut 300.. directive currently defines the amount of time Apache will wait for three things:.. The total amount of time it takes to receive a GET request.. The amount of time between receipt of TCP packets on a POST or PUT request.. The amount of time between ACKs on transmissions of TCP packets in responses.. We plan on making these separately configurable at some point down the road.. The timer used to default to 1200 before 1.. 2, but has been lowered to 300 which is still far more than necessary in most situations.. It is not set any lower by default because there may still be odd places in the code where the timer is not reset when a packet is sent.. Determines the behaviour on.. TraceEnable.. [on|off|extended].. TraceEnable on.. Available in Apache 1.. 34, 2.. 55 and later.. This directive overrides the behavior of.. for both the core server and.. The default.. permits.. requests per RFC 2616, which disallows any request body to accompany the request.. TraceEnable off.. causes the core server and.. to return a.. 405.. (Method not allowed) error to the client.. Finally, for testing and diagnostic purposes only, request bodies may be allowed using the non-compliant.. TraceEnable extended.. The core (as an origin server) will restrict the request body to 64k (plus 8k for chunk headers if.. Transfer-Encoding: chunked.. is used).. The core will reflect the full headers and all chunk headers with the response body.. As a proxy server, the request body is not restricted to 64k.. Configures how the server determines its own name and port.. UseCanonicalName On|Off|DNS.. UseCanonicalName Off.. In many situations Apache must construct a.. self-referential.. URL -- that is, a URL that refers back to the same server.. With.. UseCanonicalName On.. Apache will use the hostname and port specified in the.. directive to construct the canonical name for the server.. This name is used in all self-referential URLs, and for the values of.. SERVER_NAME.. SERVER_PORT.. in CGIs.. Apache will form self-referential URLs using the hostname and port supplied by the client if any are supplied (otherwise it will use the canonical name, as defined above).. These values are the same that are used to implement.. name based virtual hosts.. , and are available with the same clients.. The CGI variables.. will be constructed from the client supplied values as well.. An example where this may be useful is on an intranet server where you have users connecting to the machine using short names such as.. You'll notice that if the users type a shortname, and a URL which is a directory, such as.. http://www/splat.. without the trailing slash.. then Apache will redirect them to.. com/splat/.. If you have authentication enabled, this will cause the user to have to authenticate twice (once for.. and once again for.. -- see.. the FAQ on this subject for more information.. But if.. is set.. , then Apache will redirect to.. http://www/splat/.. There is a third option,.. UseCanonicalName DNS.. , which is intended for use with mass IP-based virtual hosting to support ancient clients that do not provide a.. header.. With this option Apache does a reverse DNS lookup on the server IP address that the client connected to in order to work out self-referential URLs.. Warning.. If CGIs make assumptions about the values of.. they may be broken by this option.. The client is essentially free to give whatever value they want as a hostname.. But if the CGI is only using.. to construct self-referential URLs then it should be just fine.. Listen.. UseCanonicalPhysicalPort On|Off.. UseCanonicalPhysicalPort Off.. UseCanonicalPhysicalPort On.. Apache will, when constructing the canonical port for the server to honor the.. directive, provide the actual physical port number being used by this request as a potential port.. Apache will not ever use the actual physical port number, instead relying on all configured information to construct a valid port number.. The ordering of when the physical port is used is as follows:.. Port provided in.. Servername.. Physical port.. Default port.. UseCanonicalName Off | DNS.. Parsed port from.. , the physical ports are removed from the ordering.. Contains directives that apply only to a specific hostname or IP address.. ] [.. ]].. are used to enclose a group of directives that will apply only to a particular virtual host.. Any directive that is allowed in a virtual host context may be used.. When the server receives a request for a document on a particular virtual host, it uses the configuration directives enclosed in the.. Addr.. can be:.. The IP address of the virtual host;.. A fully qualified domain name for the IP address of the virtual host;.. The character.. , which is used only in combination with.. NameVirtualHost *.. to match all IP addresses; or.. The string.. , which is used only with IP virtual hosting to catch unmatched IP addresses.. VirtualHost 10.. 3.. ServerAdmin webmaster@host.. DocumentRoot /www/docs/host.. ServerName host.. ErrorLog logs/host.. com-error_log.. TransferLog logs/host.. com-access_log.. IPv6 addresses must be specified in square brackets because the optional port number could not be determined otherwise.. An IPv6 example is shown below:.. VirtualHost [2001:db8::a00:20ff:fea7:ccea].. Each Virtual Host must correspond to a different IP address, different port number or a different host name for the server, in the former case the server machine must be configured to accept IP packets for multiple addresses.. (If the machine does not have multiple network interfaces, then this can be accomplished with the.. ifconfig alias.. command -- if your OS supports it).. The use of.. does.. affect what addresses Apache listens on.. You may need to ensure that Apache is listening on the correct addresses using.. When using IP-based virtual hosting, the special name.. can be specified in which case this virtual host will match any IP address that is not explicitly listed in another virtual host.. In the absence of any.. virtual host the "main" server config, consisting of all those definitions outside any VirtualHost section, is used when no IP-match occurs.. (But note that any IP address that matches a.. directive will use neither the "main" server config nor the.. name-based virtual hosting.. documentation for further details.. You can specify a.. :port.. to change the port that is matched.. If unspecified then it defaults to the same port as the most recent.. statement of the main server.. You may also specify.. :*.. to match all ports on that address.. (This is recommended when used with.. Setting which addresses and ports Apache uses.. Copyright 2006 The Apache Software Foundation.. Licensed under the.. Apache License, Version 2..

    Original link path: /manual/mod/core.html
    Open archive

  • Title: Apache HTTP Server Version 2.2 Documentation - Apache HTTP Server
    Descriptive info: 2 Documentation.. es.. fr.. ko.. pt-br.. Release Notes.. New features with Apache 2.. 1/2.. Upgrading to 2.. 2 from 2.. Apache License.. Reference Manual.. Compiling and Installing.. Starting.. Stopping or Restarting.. Run-time Configuration Directives.. Directive Quick-Reference.. Multi-Processing Modules (MPMs).. Handlers.. Server and Supporting Programs.. Users' Guide.. Binding.. Configuration Sections.. Content Caching.. Content Negotiation..  ...   to the Filesystem.. Performance Tuning.. Server-Wide Configuration.. SSL/TLS Encryption.. Suexec Execution for CGI.. URL Rewriting Guide.. Virtual Hosts.. How-To / Tutorials.. CGI: Dynamic Content.. htaccess files.. Server Side Includes (SSI).. Per-user Web Directories (public_html).. Platform Specific Notes.. Microsoft Windows.. Novell NetWare.. EBCDIC Port.. Other Topics.. Frequently Asked Questions.. Documentation for Developers.. Other Notes..

    Original link path: /manual/index.html
    Open archive

  • Title: Module Index - Apache HTTP Server
    Descriptive info: Module Index.. Below is a list of all of the modules that come as part of the Apache distribution.. See also the complete alphabetical list of.. all Apache directives.. Core Features and Multi-Processing Modules.. Other Modules.. Directive Quick Reference.. mpm_common.. A collection of directives that are implemented by more than one multi-processing module (MPM).. beos.. This Multi-Processing Module is optimized for BeOS.. event.. An experimental variant of the standard.. worker.. MPM.. mpm_netware.. Multi-Processing Module implementing an exclusively threaded web server optimized for Novell NetWare.. mpmt_os2.. Hybrid multi-process, multi-threaded MPM for OS/2.. prefork.. Implements a non-threaded, pre-forking web server.. mpm_winnt.. This Multi-Processing Module is optimized for Windows NT.. Multi-Processing Module implementing a hybrid multi-threaded multi-process web server.. C.. D.. E.. F.. H.. I.. L.. M.. N.. P.. R.. S.. U.. V.. This module provides for executing CGI scripts based on media type or request method.. mod_alias.. Provides for mapping different parts of the host filesystem in the document tree and for URL redirection.. mod_asis.. Sends files that contain their own HTTP headers.. Basic authentication.. User authentication using MD5 Digest Authentication.. mod_authn_alias.. Provides the ability to create extended authentication providers based on actual providers.. mod_authn_anon.. Allows "anonymous" user access to authenticated areas.. mod_authn_dbd.. User authentication using an SQL database.. mod_authn_dbm.. User authentication using DBM files.. mod_authn_default.. Authentication fallback module.. User authentication using text files.. Allows an LDAP directory to be used to store the database for HTTP Basic authentication.. Group authorization using DBM files.. mod_authz_default.. Authorization fallback module.. Group authorization using plaintext files.. Group authorizations based on host (name or IP address).. Authorization based on file ownership.. User Authorization.. Generates directory indexes, automatically, similar to the Unix.. ls.. command or the Win32.. dir.. shell command.. mod_cache.. Content cache keyed to URIs.. mod_cern_meta.. CERN httpd  ...   filter configuration module.. mod_headers.. Customization of HTTP request and response headers.. mod_ident.. RFC 1413 ident lookups.. mod_imagemap.. Server-side imagemap processing.. Server-parsed html documents (Server Side Includes).. Provides a comprehensive overview of the server configuration.. mod_isapi.. ISAPI Extensions within Apache for Windows.. mod_ldap.. LDAP connection pooling and result caching services for use by other LDAP modules.. mod_log_config.. Logging of the requests made to the server.. mod_log_forensic.. Forensic Logging of the requests made to the server.. mod_logio.. Logging of input and output bytes per request.. mod_mem_cache.. Associates the requested filename's extensions with the file's behavior (handlers and filters) and content (mime-type, language, character set and encoding).. mod_mime_magic.. Determines the MIME type of a file by looking at a few bytes of its contents.. Provides for.. content negotiation.. mod_nw_ssl.. Enable SSL encryption for NetWare.. HTTP/1.. 1 proxy/gateway server.. mod_proxy_ajp.. AJP support module for.. mod_proxy_balancer.. extension for load balancing.. mod_proxy_connect.. extension for.. request handling.. mod_proxy_ftp.. FTP support module for.. mod_proxy_http.. HTTP support module for.. Provides a rule-based rewriting engine to rewrite requested URLs on the fly.. mod_setenvif.. Allows the setting of environment variables based on characteristics of the request.. mod_so.. Loading of executable code and modules into the server at start-up or restart time.. mod_speling.. Attempts to correct mistaken URLs that users might have entered by ignoring capitalization and by allowing up to one misspelling.. mod_ssl.. Strong cryptography using the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols.. mod_status.. Provides information on server activity and performance.. mod_suexec.. Allows CGI scripts to run as a specified user and Group.. mod_unique_id.. Provides an environment variable with a unique identifier for each request.. mod_userdir.. User-specific directories.. mod_usertrack.. Clickstream.. logging of user activity on a site.. mod_version.. Version dependent configuration.. mod_vhost_alias.. Provides for dynamically configured mass virtual hosting..

    Original link path: /manual/mod/
    Open archive

  • Title: Directive Index - Apache HTTP Server
    Descriptive info: Directive Index.. ru.. Each Apache directive available in the standard Apache distribution is listed here.. They are described using a consistent format, and there is.. a dictionary.. of the terms used in their descriptions available.. is also available giving details about each directive in a summary form.. B.. G.. K.. O.. T.. W.. X.. AcceptMutex.. AddAlt.. AddAltByEncoding.. AddAltByType.. AddEncoding.. AddLanguage.. AddModuleInfo.. AliasMatch.. AllowCONNECT.. Anonymous.. Anonymous_LogEmail.. Anonymous_MustGiveEmail.. Anonymous_NoUserID.. Anonymous_VerifyEmail.. AuthBasicAuthoritative.. AuthBasicProvider.. AuthDBDUserPWQuery.. AuthDBDUserRealmQuery.. AuthDBMType.. AuthDefaultAuthoritative.. AuthDigestAlgorithm.. AuthDigestDomain.. AuthDigestNcCheck.. AuthDigestNonceFormat.. AuthDigestNonceLifetime.. AuthDigestProvider.. AuthDigestQop.. AuthDigestShmemSize.. AuthLDAPBindDN.. AuthLDAPBindPassword.. AuthLDAPCharsetConfig.. AuthLDAPCompareDNOnServer.. AuthLDAPDereferenceAliases.. AuthLDAPGroupAttribute.. AuthLDAPGroupAttributeIsDN.. AuthLDAPRemoteUserIsDN.. AuthLDAPUrl.. AuthnProviderAlias.. AuthzDBMAuthoritative.. AuthzDBMType.. AuthzDefaultAuthoritative.. AuthzGroupFileAuthoritative.. AuthzLDAPAuthoritative.. AuthzOwnerAuthoritative.. AuthzUserAuthoritative.. BrowserMatchNoCase.. BufferedLogs.. CacheDefaultExpire.. CacheDirLength.. CacheDirLevels.. CacheDisable.. CacheEnable.. CacheFile.. CacheIgnoreCacheControl.. CacheIgnoreHeaders.. CacheIgnoreNoLastMod.. CacheLastModifiedFactor.. CacheMaxExpire.. CacheMaxFileSize.. CacheMinFileSize.. CacheNegotiatedDocs.. CacheRoot.. CacheStoreNoStore.. CacheStorePrivate.. CharsetDefault.. CharsetOptions.. CharsetSourceEnc.. CheckSpelling.. CookieLog.. CoreDumpDirectory.. CustomLog.. Dav.. DavDepthInfinity.. DavGenericLockDB.. DavLockDB.. DavMinTimeout.. DBDExptime.. DBDKeep.. DBDMax.. DBDMin.. DBDParams.. DBDPersist.. DBDPrepareSQL..  ...   LDAPTrustedGlobalCert.. LDAPTrustedMode.. LDAPVerifyServerCert.. ListenBackLog.. LoadFile.. LockFile.. LogFormat.. MaxClients.. MaxMemFree.. MaxRequestsPerChild.. MaxRequestsPerThread.. MaxSpareServers.. MaxSpareThreads.. MaxThreads.. MCacheMaxObjectCount.. MCacheMaxObjectSize.. MCacheMaxStreamingBuffer.. MCacheMinObjectSize.. MCacheRemovalAlgorithm.. MCacheSize.. MetaDir.. MetaFiles.. MetaSuffix.. MimeMagicFile.. MinSpareServers.. MinSpareThreads.. MMapFile.. ModMimeUsePathInfo.. MultiviewsMatch.. NoProxy.. NWSSLTrustedCerts.. NWSSLUpgradeable.. PassEnv.. PidFile.. ProtocolEcho.. Proxy.. ProxyBadHeader.. ProxyBlock.. ProxyDomain.. ProxyErrorOverride.. ProxyIOBufferSize.. ProxyMatch.. ProxyMaxForwards.. ProxyPass.. ProxyPassReverse.. ProxyPassReverseCookieDomain.. ProxyPassReverseCookiePath.. ProxyPreserveHost.. ProxyReceiveBufferSize.. ProxyRemote.. ProxyRemoteMatch.. ProxyRequests.. ProxyTimeout.. ProxyVia.. ReceiveBufferSize.. Redirect.. RedirectMatch.. RedirectPermanent.. RedirectTemp.. RemoveCharset.. RemoveEncoding.. RemoveHandler.. RemoveInputFilter.. RemoveLanguage.. RemoveOutputFilter.. RemoveType.. RewriteLock.. RewriteLog.. RewriteLogLevel.. RewriteMap.. ScoreBoardFile.. ScriptAliasMatch.. ScriptLog.. ScriptLogBuffer.. ScriptLogLength.. ScriptSock.. SecureListen.. SendBufferSize.. ServerLimit.. SetEnv.. SSIEndTag.. SSIErrorMsg.. SSIStartTag.. SSITimeFormat.. SSIUndefinedEcho.. SSLCACertificateFile.. SSLCACertificatePath.. SSLCADNRequestFile.. SSLCADNRequestPath.. SSLCARevocationFile.. SSLCARevocationPath.. SSLCertificateChainFile.. SSLCertificateFile.. SSLCertificateKeyFile.. SSLCipherSuite.. SSLCryptoDevice.. SSLEngine.. SSLHonorCipherOrder.. SSLMutex.. SSLOptions.. SSLPassPhraseDialog.. SSLProtocol.. SSLProxyCACertificateFile.. SSLProxyCACertificatePath.. SSLProxyCARevocationFile.. SSLProxyCARevocationPath.. SSLProxyCipherSuite.. SSLProxyEngine.. SSLProxyMachineCertificateFile.. SSLProxyMachineCertificatePath.. SSLProxyProtocol.. SSLProxyVerify.. SSLProxyVerifyDepth.. SSLRandomSeed.. SSLRequire.. SSLRequireSSL.. SSLSessionCache.. SSLSessionCacheTimeout.. SSLUserName.. SSLVerifyClient.. SSLVerifyDepth.. StartServers.. StartThreads.. SuexecUserGroup.. ThreadLimit.. ThreadsPerChild.. ThreadStackSize.. TransferLog.. TypesConfig.. UnsetEnv.. User.. UserDir.. VirtualDocumentRoot.. VirtualDocumentRootIP.. VirtualScriptAlias.. VirtualScriptAliasIP.. Win32DisableAcceptEx..

    Original link path: /manual/mod/directives.html
    Open archive

  • Title: Frequently Asked Questions - Apache HTTP Server
    Descriptive info: The latest version of this FAQ is always available from the main Apache web site, at.. http://httpd.. apache.. org/docs/2.. 2/faq/.. In addition, you can view this FAQ.. all in one page.. for easy searching and printing.. If you don't find the answer to your question in the below sections, please also consult the.. Apache 1.. 3 FAQ.. to see if your question is answered there.. Topics.. Background.. Background information about the Apache HTTP Server.. Support.. What do I do when I have problems?.. Error Messages.. What does this error message mean?..

    Original link path: /manual/faq/
    Open archive

  • Title: Glossary - Apache HTTP Server
    Descriptive info: This glossary defines some of the common terminology related to Apache in particular, and web serving in general.. More information on each concept is provided in the links.. Definitions.. Access Control.. The restriction of access to network realms.. In an Apache context usually the restriction of access to certain.. URLs.. See:.. Algorithm.. An unambiguous formula or set of rules for solving a problem in a finite number of steps.. Algorithms for encryption are usually called.. Ciphers.. APache eXtension Tool.. (apxs).. A perl script that aids in compiling.. sources into Dynamic Shared Objects (.. DSO.. s) and helps install them in the Apache Web server.. See: Manual Page:.. apxs.. Apache Portable Runtime.. (APR).. A set of libraries providing many of the basic interfaces between the server and the operating system.. APR is developed parallel to the Apache HTTP Server as an independent project.. Apache Portable Runtime Project.. Authentication.. The positive identification of a network entity such as a server, a client, or a user.. Certificate.. A data record used for authenticating network entities such as a server or a client.. A certificate contains X.. 509 information pieces about its owner (called the subject) and the signing.. Certification Authority.. (called the issuer), plus the owner's.. public key.. and the signature made by the CA.. Network entities verify these signatures using CA certificates.. Certificate Signing Request.. (CSR).. An unsigned.. certificate.. for submission to a.. , which signs it with the.. Private Key.. of their CA.. Once the CSR is signed, it becomes a real certificate.. (CA).. A trusted third party whose purpose is to sign certificates for network entities it has authenticated using secure means.. Other network entities can check the signature to verify that a CA has authenticated the bearer of a certificate.. Cipher.. An algorithm or system for data encryption.. Examples are DES, IDEA, RC4, etc.. Ciphertext.. The result after.. Plaintext.. is passed through a.. Common Gateway Interface.. (CGI).. A standard definition for an interface between a web server and an external program that allows the external program to service requests.. The interface was originally defined by.. NCSA.. but there is also an.. RFC project.. Dynamic Content with CGI.. Configuration Directive.. Configuration File.. A text file containing.. that control the configuration of Apache.. An HTTP.. for proxying raw data channels over HTTP.. It can be used to encapsulate other protocols, such as the SSL protocol.. An area in the.. configuration files.. where certain types of.. are allowed.. Terms Used to Describe Apache Directives.. Digital Signature.. An encrypted text block that validates a certificate or other file.. creates a signature by generating a hash of the.. Public Key.. embedded in a.. , then encrypting the hash with its own.. Only the CA's public key can decrypt the signature, verifying that the CA has authenticated the network entity that owns the.. A configuration command that controls one or more aspects of Apache's behavior.. Directives are placed in the.. Dynamic Shared Object.. (DSO).. compiled separately from the Apache.. binary that can be loaded on-demand.. Dynamic Shared Object Support.. Environment Variable.. (env-variable).. Named variables managed by the operating system shell and used to store information and communicate between programs.. Apache also contains internal variables that are referred to as environment variables, but are stored in internal Apache structures, rather than in the shell environment.. Environment Variables in Apache.. Export-Crippled.. Diminished in cryptographic strength (and security) in order to comply with the United States' Export Administration Regulations (EAR).. Export-crippled cryptographic software is limited to a small key size, resulting in.. which usually can be decrypted by brute force.. Filter.. A process that is applied to data that is sent or received by the server.. Input filters process data sent by the client to the server, while output filters process documents on the server before they are sent to the client.. For example, the.. output filter processes documents for.. Server Side Includes.. Fully-Qualified Domain-Name.. (FQDN).. The unique name of a network entity, consisting of a hostname and a domain name that can resolve to an IP address.. is a hostname,.. example.. is a domain name, and.. is a fully-qualified domain name.. Handler.. An internal Apache representation of the action to be performed when a file is called.. Generally, files have implicit handlers, based on the file type.. Normally,  ...   that are included by default are called.. base modules.. Many modules are available for Apache that are not distributed as part of the Apache HTTP Server.. tarball.. These are referred to as.. third-party modules.. Module Magic Number.. MMN.. Module Magic Number is a constant defined in the Apache source code that is associated with binary compatibility of modules.. It is changed when internal Apache structures, function calls and other significant parts of API change in such a way that binary compatibility cannot be guaranteed any more.. On MMN change, all third party modules have to be at least recompiled, sometimes even slightly changed in order to work with the new version of Apache.. OpenSSL.. The Open Source toolkit for SSL/TLS.. See.. openssl.. org/.. Pass Phrase.. The word or phrase that protects private key files.. It prevents unauthorized users from encrypting them.. Usually it's just the secret encryption/decryption key used for.. The unencrypted text.. The secret key in a.. Public Key Cryptography.. system, used to decrypt incoming messages and sign outgoing ones.. Proxy.. An intermediate server that sits between the client and the.. origin server.. It accepts requests from clients, transmits those requests on to the origin server, and then returns the response from the origin server to the client.. If several clients request the same content, the proxy can deliver that content from its cache, rather than requesting it from the origin server each time, thereby reducing response time.. The publicly available key in a.. system, used to encrypt messages bound for its owner and to decrypt signatures made by its owner.. The study and application of asymmetric encryption systems, which use one key for encryption and another for decryption.. A corresponding pair of such keys constitutes a key pair.. Also called Asymmetric Cryptography.. Regular Expression.. (Regex).. A way of describing a pattern in text - for example, "all the words that begin with the letter A" or "every 10-digit phone number" or even "Every sentence with two commas in it, and no capital letter Q".. Regular expressions are useful in Apache because they let you apply certain attributes against collections of files or resources in very flexible ways - for example, all.. gif and.. jpg files under any "images" directory could be written as ".. /images/.. *(jpg|gif)$.. ".. Apache uses Perl Compatible Regular Expressions provided by the.. PCRE.. library.. Reverse Proxy.. proxy.. server that appears to the client as if it is an.. This is useful to hide the real origin server from the client for security reasons, or to load balance.. Secure Sockets Layer.. (SSL).. A protocol created by Netscape Communications Corporation for general communication authentication and encryption over TCP/IP networks.. The most popular usage is.. , i.. the HyperText Transfer Protocol (HTTP) over SSL.. (SSI).. A technique for embedding processing directives inside HTML files.. Introduction to Server Side Includes.. Session.. The context information of a communication in general.. SSLeay.. The original SSL/TLS implementation library developed by Eric A.. Young.. Symmetric Cryptography.. The study and application of.. that use a single secret key for both encryption and decryption operations.. Tarball.. A package of files gathered together using the.. tar.. utility.. Apache distributions are stored in compressed tar archives or using pkzip.. Transport Layer Security.. (TLS).. The successor protocol to SSL, created by the Internet Engineering Task Force (IETF) for general communication authentication and encryption over TCP/IP networks.. TLS version 1 and is nearly identical with SSL version 3.. Uniform Resource Locator.. (URL).. The name/address of a resource on the Internet.. This is the common informal term for what is formally called a.. Uniform Resource Identifier.. URLs are usually made up of a scheme, like.. https.. , a hostname, and a path.. A URL for this page might be.. 2/glossary.. (URI).. A compact string of characters for identifying an abstract or physical resource.. It is formally defined by.. RFC 2396.. URIs used on the world-wide web are commonly referred to as.. Virtual Hosting.. Serving multiple websites using a single instance of Apache.. IP virtual hosting.. differentiates between websites based on their IP address, while.. uses only the name of the host and can therefore host many sites on the same IP address.. X.. 509.. An authentication certificate scheme recommended by the International Telecommunication Union (ITU-T) which is used for SSL/TLS authentication..

    Original link path: /manual/glossary.html
    Open archive

  • Title: Sitemap - Apache HTTP Server
    Descriptive info: This page lists the currently available documents of the.. Using the Apache HTTP Server.. Apache Server Frequently Asked Questions.. Apache SSL/TLS Encryption.. Guides, Tutorials, and HowTos.. Platform-specific Notes.. Apache HTTP Server and Supporting Programs.. Apache Miscellaneous Documentation.. Apache modules.. Developer Documentation.. Glossary and Index.. Compiling and Installing Apache.. Starting Apache.. Stopping and Restarting the Server.. How Directory, Location and Files sections work.. Mapping URLs to Filesystem Locations.. Dynamic Shared Object (DSO) support.. Custom error responses.. suEXEC Support.. Performance Hints.. Overview.. Name-based Virtual Hosts.. IP-based Virtual Host Support.. Dynamically configured mass virtual hosting.. VirtualHost Examples.. An In-Depth Discussion of Virtual Host Matching.. File descriptor limitations.. Background Information.. SSL/TLS Encryption: An Introduction.. SSL/TLS Encryption: Compatibility.. SSL/TLS Encryption: How-To.. SSL/TLS Encryption: FAQ.. Per-user web directories.. Using Apache with Microsoft Windows.. Compiling Apache for Microsoft Windows.. Using Apache with Novell NetWare.. Running a High-Performance Web Server on HPUX.. The Apache EBCDIC Port.. Manual Page: httpd.. Manual Page: ab.. Manual Page: apachectl.. Manual Page: apxs.. Manual Page: configure.. Manual Page: dbmmanage.. Manual Page: htcacheclean.. Manual Page: htdbm.. Manual Page: htdigest.. Manual Page: htpasswd.. Manual Page: logresolve.. Manual Page: rotatelogs.. Manual Page: suexec.. Other Programs.. Relevant Standards.. Definitions of terms used to describe Apache modules.. Definitions of terms used to describe Apache directives.. Apache  ...   Apache Module mod_authz_owner.. Apache Module mod_authz_user.. Apache Module mod_autoindex.. Apache Module mod_cache.. Apache Module mod_cern_meta.. Apache Module mod_cgi.. Apache Module mod_cgid.. Apache Module mod_charset_lite.. Apache Module mod_dav.. Apache Module mod_dav_fs.. Apache Module mod_dav_lock.. Apache Module mod_dbd.. Apache Module mod_deflate.. Apache Module mod_dir.. Apache Module mod_disk_cache.. Apache Module mod_dumpio.. Apache Module mod_echo.. Apache Module mod_env.. Apache Module mod_example.. Apache Module mod_expires.. Apache Module mod_ext_filter.. Apache Module mod_file_cache.. Apache Module mod_filter.. Apache Module mod_headers.. Apache Module mod_ident.. Apache Module mod_imagemap.. Apache Module mod_include.. Apache Module mod_info.. Apache Module mod_isapi.. Apache Module mod_ldap.. Apache Module mod_log_config.. Apache Module mod_log_forensic.. Apache Module mod_logio.. Apache Module mod_mem_cache.. Apache Module mod_mime.. Apache Module mod_mime_magic.. Apache Module mod_negotiation.. Apache Module mod_nw_ssl.. Apache Module mod_proxy.. Apache Module mod_proxy_ajp.. Apache Module mod_proxy_balancer.. Apache Module mod_proxy_connect.. Apache Module mod_proxy_ftp.. Apache Module mod_proxy_http.. Apache Module mod_rewrite.. Apache Module mod_setenvif.. Apache Module mod_so.. Apache Module mod_speling.. Apache Module mod_ssl.. Apache Module mod_status.. Apache Module mod_suexec.. Apache Module mod_unique_id.. Apache Module mod_userdir.. Apache Module mod_usertrack.. Apache Module mod_version.. Apache Module mod_vhost_alias.. Apache API notes.. Debugging Memory Allocation in APR.. Documenting Apache 2.. Apache 2.. 0 Hook Functions.. Converting Modules from Apache 1.. 3 to Apache 2.. Request Processing in Apache 2.. How Filters Work in Apache 2.. Module index.. Directive index..

    Original link path: /manual/sitemap.html
    Open archive

  • Title: Terms Used to Describe Modules - Apache HTTP Server
    Descriptive info: Terms Used to Describe Modules.. This document describes the terms that are used to describe each Apache.. Status.. Source File.. Module Identifier.. Compatibility.. A brief description of the purpose of the module.. This indicates how tightly bound into the Apache Web server the module is; in other words, you may need to recompile the server in order to gain access to the module and its functionality.. Possible values for this attribute are:.. A module with status "MPM" is a.. Multi-Processing Module.. Unlike the other types of modules, Apache must have one and only one MPM in use at any time.. This type of module is responsible for basic request handling and dispatching.. Base.. A module labeled as having "Base" status is compiled and loaded into the server by default, and is therefore normally available unless you have taken steps to remove the module from your configuration.. Extension.. A  ...   your own if you try to use it.. The module is being documented for completeness, and is not necessarily supported.. External.. Modules which are not included with the base Apache distribution ("third-party modules") may use the "External" status.. We are not responsible for, nor do we support such modules.. This quite simply lists the name of the source file which contains the code for the module.. This is also the name used by the.. This is a string which identifies the module for use in the.. directive when dynamically loading modules.. In particular, it is the name of the external variable of type module in the source file.. If the module was not part of the original Apache version 2 distribution, the version in which it was introduced should be listed here.. In addition, if the module is limited to particular platforms, the details will be listed here..

    Original link path: /manual/mod/module-dict.html
    Open archive

  • Title: Terms Used to Describe Directives - Apache HTTP Server
    Descriptive info: Terms Used to Describe Directives.. configuration directive.. Syntax.. Override.. Configuration files.. A brief description of the purpose of the directive.. This indicates the format of the directive as it would appear in a configuration file.. This syntax is extremely directive-specific, and is described in detail in the directive's definition.. Generally, the directive name is followed by a series of one or more space-separated arguments.. If an argument contains a space, the argument must be enclosed in double quotes.. Optional arguments are enclosed in square brackets.. Where an argument can take on more than one possible value, the possible values are separated by vertical bars "|".. Literal text is presented in the default font, while argument-types for which substitution is necessary are.. emphasized.. Directives which can take a variable number of arguments will end in ".. " indicating that the last argument is repeated.. Directives use a great number of different argument types.. A few common ones are defined below.. A complete Uniform Resource Locator including a scheme, hostname, and optional pathname as in.. com/path/to/file.. The part of a.. url.. which follows the scheme and hostname as in.. /path/to/file.. url-path.. represents a web-view of a resource, as opposed to a file-system view.. The path to a file in the local file-system beginning with the root directory as in.. /usr/local/apache/htdocs/path/to/file.. Unless otherwise specified, a.. which does not begin with a slash will be treated as relative to the.. The path to a directory in the local file-system beginning with the root directory as in.. /usr/local/apache/htdocs/path/to/.. The name of a file with no accompanying path information as in.. A Perl-compatible.. The directive definition will specify what the.. is matching against.. In general, this is the part of the.. which follows the last dot.. However, Apache recognizes multiple filename extensions, so if a.. contains more than one dot, each dot-separated part of the filename following the first dot is an.. en.. contains two extensions:.. For Apache directives, you may specify.. s with or without the leading dot.. In addition,.. s are not case sensitive.. A method of describing the format of a file which consists of a major format type and a minor format type, separated by a slash as in.. env-variable.. The name of an.. defined in the Apache configuration process.. Note this is not necessarily the same as an operating system environment variable.. environment variable documentation.. If the directive has a default value (.. , if you omit it from your configuration entirely, the Apache Web server will behave as though you set it to a particular value), it is described here.. If there is  ...   OR of all of the listed contexts.. In other words, a directive that is marked as being valid in ".. server config,.. " can be used in the.. file and in.. files, but not within any.. This directive attribute indicates which configuration override must be active in order for the directive to be processed when it appears in a.. If the directive's.. context.. doesn't permit it to appear in.. files, then no context will be listed.. Overrides are activated by the.. directive, and apply to a particular scope (such as a directory) and all descendants, unless further modified by other.. directives at lower levels.. The documentation for that directive also lists the possible override names available.. This indicates how tightly bound into the Apache Web server the directive is; in other words, you may need to recompile the server with an enhanced set of modules in order to gain access to the directive and its functionality.. If a directive is listed as having "Core" status, that means it is part of the innermost portions of the Apache Web server, and is always available.. A directive labeled as having "MPM" status is provided by a.. This type of directive will be available if and only if you are using one of the MPMs listed on the.. line of the directive definition.. A directive labeled as having "Base" status is supported by one of the standard Apache modules which is compiled into the server by default, and is therefore normally available unless you've taken steps to remove the module from your configuration.. A directive with "Extension" status is provided by one of the modules included with the Apache server kit, but the module isn't normally compiled into the server.. To enable the directive and its functionality, you will need to change the server build configuration files and re-compile Apache.. "Experimental" status indicates that the directive is available as part of the Apache kit, but you're on your own if you try to use it.. The directive is being documented for completeness, and is not necessarily supported.. The module which provides the directive may or may not be compiled in by default; check the top of the page which describes the directive and its module to see if it remarks on the availability.. This quite simply lists the name of the source module which defines the directive.. If the directive wasn't part of the original Apache version 2 distribution, the version in which it was introduced should be listed here.. In addition, if the directive is available only on certain platforms, it will be noted here..

    Original link path: /manual/mod/directive-dict.html
    Open archive

  • Title: Apache's Handler Use - Apache HTTP Server
    Descriptive info: This document describes the use of Apache's Handlers.. What is a Handler.. Examples.. Programmer's Note.. Related Modules.. Related Directives.. A "handler" is an internal Apache representation of the action to be performed when a file is called.. Handlers may also be configured explicitly, based on either filename extensions or on location, without relation to file type.. This is advantageous both because it is a more elegant solution, and because it also allows for both a type.. a handler to be associated with a file.. (See also.. Files with Multiple Extensions.. Handlers can either be built into the server or included in a module, or they can be added with the.. The built-in handlers in the standard distribution are as follows:.. default-handler.. : Send the file using the.. default_handler().. , which is the handler used by default to handle static content.. (core).. send-as-is.. : Send file with HTTP headers as is.. : Treat the file as a CGI script.. imap-file.. : Parse as an imagemap rule file.. server-info.. : Get the server's configuration information.. server-status.. :  ...   requested document (pointed to by the.. PATH_TRANSLATED.. environment variable) and making whatever modifications or additions are desired.. Files with HTTP headers.. The following directives will enable the.. handler, which is used for files which contain their own HTTP headers.. All files in the.. /web/htdocs/asis/.. directory will be processed by the.. handler, regardless of their filename extensions.. Directory /web/htdocs/asis.. SetHandler send-as-is.. In order to implement the handler features, an addition has been made to the.. Apache API.. that you may wish to make use of.. Specifically, a new record has been added to the.. request_rec.. structure:.. char *handler.. If you wish to have your module engage a handler, you need only to set.. r- handler.. to the name of the handler at any time prior to the.. invoke_handler.. stage of the request.. Handlers are implemented as they were before, albeit using the handler name instead of a content type.. While it is not necessary, the naming convention for handlers is to use a dash-separated word, with no slashes, so as to not invade the media type name-space..

    Original link path: /manual/handler.html
    Open archive


    Archived pages: 174