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

Total: 175

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

Or switch to "Titles and links view".
  • Terms Used to Describe Modules - Apache HTTP Server
    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 module with Extension status is not normally compiled and loaded into the server To enable the module and its functionality you may need to change the server build configuration files and re compile Apache Experimental Experimental status indicates that the module is available as part of the Apache kit but you are on 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 Source File This quite simply lists the name of the source file which contains the code for the module This is also the name used

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


  • Terms Used to Describe Directives - Apache HTTP Server
    one dot each dot separated part of the filename following the first dot is an extension For example the filename file html en contains two extensions html and en For Apache directives you may specify extension s with or without the leading dot In addition extension s are not case sensitive MIME type 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 text html env variable The name of an environment variable defined in the Apache configuration process Note this is not necessarily the same as an operating system environment variable See the environment variable documentation for more details Default If the directive has a default value i e 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 no default value this section should say None Note that the default listed here is not necessarily the same as the value the directive takes in the default httpd conf distributed with the server Context This indicates where in the server s configuration files the directive is legal It s a comma separated list of one or more of the following values server config This means that the directive may be used in the server configuration files e g httpd conf but not within any VirtualHost or Directory containers It is not allowed in htaccess files at all virtual host This context means that the directive may appear inside VirtualHost containers in the server configuration files directory A directive marked as being valid in this context may be used inside Directory Location Files and Proxy containers in the server configuration files subject to the restrictions outlined in Configuration Sections htaccess If a directive is valid in this context it means that it can appear inside per directory htaccess files It may not be processed though depending upon the overrides currently active The directive is only allowed within the designated context if you try to use it elsewhere you ll get a configuration error that will either prevent the server from handling requests in that context correctly or will keep the server from operating at all i e the server won t even start The valid locations for the directive are actually the result of a Boolean OR of all of the listed contexts In other words a directive that is marked as being valid in server config htaccess can be used in the httpd conf file and in htaccess files but not within any Directory or VirtualHost containers Override This directive attribute indicates which configuration override must be active in order for the directive to be processed when it appears in a htaccess file If the directive s context doesn t permit it to appear in htaccess files then no context will be listed Overrides are activated by the AllowOverride directive and apply

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

  • Apache's Handler Use - Apache HTTP Server
    relation to file type This is advantageous both because it is a more elegant solution and because it also allows for both a type and 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 Action directive 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 mod asis cgi script Treat the file as a CGI script mod cgi imap file Parse as an imagemap rule file mod imagemap server info Get the server s configuration information mod info server status Get the server s status report mod status type map Parse as a type map file for content negotiation mod negotiation Examples Modifying static content using a CGI script The following directives will cause requests for files with the html extension to trigger the launch of the footer pl CGI script Action add footer cgi bin footer pl AddHandler add footer html Then the CGI script is responsible for sending the originally 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 send as is 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 send as is handler regardless of their filename extensions Directory web htdocs asis SetHandler send as is Directory Programmer s Note In order to implement the handler features an addition has been made to

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

  • mod_cgi - Apache HTTP Server

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


  • mod_isapi - Apache HTTP Server

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


  • Filters - Apache HTTP Server
    request processing phases Some examples of filtering in the standard Apache distribution are mod include implements server side includes mod ssl implements SSL encryption https mod deflate implements compression decompression on the fly mod charset lite transcodes between different character sets mod ext filter runs an external program as a filter Apache also uses a number of filters internally to perform functions like chunking and byte range handling A wider range of applications are implemented by third party filter modules available from modules apache org and elsewhere A few of these are HTML and XML processing and rewriting XSLT transforms and XIncludes XML Namespace support File Upload handling and decoding of HTML Forms Image processing Protection of vulnerable applications such as PHP scripts Text search and replace editing Smart Filtering mod filter included in Apache 2 1 and later enables the filter chain to be configured dynamically at run time So for example you can set up a proxy to rewrite HTML with an HTML filter and JPEG images with a completely separate filter despite the proxy having no prior information about what the origin server will send This works by using a filter harness that dispatches to different providers according to the actual contents at runtime Any filter may be either inserted directly in the chain and run unconditionally or used as a provider and inserted dynamically For example an HTML processing filter will only run if the content is text html or application xhtml xml A compression filter will only run if the input is a compressible type and not already compressed A charset conversion filter will be inserted if a text document is not already in the desired charset Using Filters There are two ways to use filtering Simple and Dynamic In general you should use one

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

  • mod_include - Apache HTTP Server

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


  • Configuration Files - Apache HTTP Server
    are often case sensitive Lines that begin with the hash character are considered comments and are ignored Comments may not be included on a line after a configuration directive Blank lines and white space occurring before a directive are ignored so you may indent directives for clarity You can check your configuration files for syntax errors without starting the server by using apachectl configtest or the t command line option Modules Related Modules Related Directives mod so IfModule LoadModule Apache is a modular server This implies that only the most basic functionality is included in the core server Extended features are available through modules which can be loaded into Apache By default a base set of modules is included in the server at compile time If the server is compiled to use dynamically loaded modules then modules can be compiled separately and added at any time using the LoadModule directive Otherwise Apache must be recompiled to add or remove modules Configuration directives may be included conditional on a presence of a particular module by enclosing them in an IfModule block To see which modules are currently compiled into the server you can use the l command line option Scope of Directives Related Modules Related Directives Directory DirectoryMatch Files FilesMatch Location LocationMatch VirtualHost Directives placed in the main configuration files apply to the entire server If you wish to change the configuration for only a part of the server you can scope your directives by placing them in Directory DirectoryMatch Files FilesMatch Location and LocationMatch sections These sections limit the application of the directives which they enclose to particular filesystem locations or URLs They can also be nested allowing for very fine grained configuration Apache has the capability to serve many different websites simultaneously This is called Virtual Hosting Directives can

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



  •