This document summarizes the Apache Quick Reference Card which provides information on Apache directives, configuration options, and variables. It lists Apache directives alphabetically with their arguments, defaults, module/context, and whether they are new in version 1.3. It also includes sections on command line options, general configuration directives, logging directives, and more.
Apache Con NA 2013 - Cassandra Internalsaaronmorton
The document provides an overview of the architecture and internals of Apache Cassandra. It discusses the client-facing API layer including Thrift, CQL, JMX, and CLI. It then covers the Dynamo layer which handles messaging, distributed hash tables, replication strategies, and gossip protocols. Finally, it summarizes the database layer for managing tables, columns, memtables, SSTables, and read/write paths.
Apache Cassandra in Bangalore - Cassandra Internals and Performanceaaronmorton
Cassandra internals and performance was presented. The key points covered include:
1) Cassandra has a layered architecture with APIs, a Dynamo layer, and a database layer. The Dynamo layer implements the Dynamo paper and handles replication and failure handling.
2) The database layer includes the memtable, SSTables, commit log and more. It handles writes, flushes, compactions and reads from storage.
3) A number of performance tests were shown measuring the impact of configuration parameters like memtable flush queue size, commit log sync period, and secondary indexes on write and read latency. Bloom filters, compactions and concurrency were also discussed.
Hacking an ASP.NET website is possible, though difficult. The document discusses vulnerabilities in ASP.NET applications that could allow an attacker to bypass restrictions or execute code. It notes that interacting with native libraries and using mixed assemblies could enable arbitrary code execution if vulnerabilities are present. Insecure managed code, integer overflows, and hash collisions are also discussed as potential attack vectors. The document advocates testing restrictions bypassing, file inclusion vulnerabilities, and other methods of exploiting ASP.NET applications.
The document describes the architecture of Cassandra, including its startup process, layers (API, Dynamo, database), services (StorageProxy, MessagingService, Gossip), and failure handling. It also details how nodes communicate via the Gossip protocol to exchange state information and maintain a consistent cluster view.
RailswayCon 2010 - Dynamic Language VMsLourens Naudé
The document discusses Ruby virtual machines and optimizations. It covers topics like Ruby VM internals, system resources, Ruby optimizations like constant folding and inlining, object structures, classes and modules, method dispatch, garbage collection. The goal is to understand tools and techniques for building high performance Ruby applications.
This document provides an introduction to Snort rule syntax and content matching. It describes the basic components of a Snort rule including the rule header, action, protocols, addresses, ports, and rule options. It then covers various content matching techniques like content, pcre, and content modifiers like nocase, offset, depth, distance, and within. It also discusses negated content matching, content buffers, and fast_pattern. Finally, it provides examples of how content matching can be used for detection strategies like traffic triage and isolating vulnerable application traffic.
ASP.NET websites can be vulnerable to attacks like file inclusion and remote code execution if they do not properly sanitize user-supplied input, as features like Response.WriteFile and Server.Execute could allow an attacker to read arbitrary files or execute code if passed a malicious file path. The ViewState, Request Validation, and Event Validation features also have weaknesses that could allow attacks like cross-site scripting or request forgery if not implemented correctly.
Apache Con NA 2013 - Cassandra Internalsaaronmorton
The document provides an overview of the architecture and internals of Apache Cassandra. It discusses the client-facing API layer including Thrift, CQL, JMX, and CLI. It then covers the Dynamo layer which handles messaging, distributed hash tables, replication strategies, and gossip protocols. Finally, it summarizes the database layer for managing tables, columns, memtables, SSTables, and read/write paths.
Apache Cassandra in Bangalore - Cassandra Internals and Performanceaaronmorton
Cassandra internals and performance was presented. The key points covered include:
1) Cassandra has a layered architecture with APIs, a Dynamo layer, and a database layer. The Dynamo layer implements the Dynamo paper and handles replication and failure handling.
2) The database layer includes the memtable, SSTables, commit log and more. It handles writes, flushes, compactions and reads from storage.
3) A number of performance tests were shown measuring the impact of configuration parameters like memtable flush queue size, commit log sync period, and secondary indexes on write and read latency. Bloom filters, compactions and concurrency were also discussed.
Hacking an ASP.NET website is possible, though difficult. The document discusses vulnerabilities in ASP.NET applications that could allow an attacker to bypass restrictions or execute code. It notes that interacting with native libraries and using mixed assemblies could enable arbitrary code execution if vulnerabilities are present. Insecure managed code, integer overflows, and hash collisions are also discussed as potential attack vectors. The document advocates testing restrictions bypassing, file inclusion vulnerabilities, and other methods of exploiting ASP.NET applications.
The document describes the architecture of Cassandra, including its startup process, layers (API, Dynamo, database), services (StorageProxy, MessagingService, Gossip), and failure handling. It also details how nodes communicate via the Gossip protocol to exchange state information and maintain a consistent cluster view.
RailswayCon 2010 - Dynamic Language VMsLourens Naudé
The document discusses Ruby virtual machines and optimizations. It covers topics like Ruby VM internals, system resources, Ruby optimizations like constant folding and inlining, object structures, classes and modules, method dispatch, garbage collection. The goal is to understand tools and techniques for building high performance Ruby applications.
This document provides an introduction to Snort rule syntax and content matching. It describes the basic components of a Snort rule including the rule header, action, protocols, addresses, ports, and rule options. It then covers various content matching techniques like content, pcre, and content modifiers like nocase, offset, depth, distance, and within. It also discusses negated content matching, content buffers, and fast_pattern. Finally, it provides examples of how content matching can be used for detection strategies like traffic triage and isolating vulnerable application traffic.
ASP.NET websites can be vulnerable to attacks like file inclusion and remote code execution if they do not properly sanitize user-supplied input, as features like Response.WriteFile and Server.Execute could allow an attacker to read arbitrary files or execute code if passed a malicious file path. The ViewState, Request Validation, and Event Validation features also have weaknesses that could allow attacks like cross-site scripting or request forgery if not implemented correctly.
This document discusses the configuration of various server services, including:
- Setting up an Apache web server with SSL encryption and generating SSL certificates.
- Additional Apache configurations like virtual hosting, CGI scripts, and SELinux contexts.
- Basic SMTP configuration using Postfix and setting up an internal mail server.
- Configuring a caching-only DNS server using Named.
- Setting up NFS for file sharing between servers.
- Enabling file sharing with Windows clients using Samba (CIFS).
- Configuring an anonymous FTP server with vsftpd.
It provides instructions and examples for configuring each of these services on Linux servers.
Cmake is a cross-platform build system generator that allows users to specify platform-independent build processes. It generates native makefiles and workspaces that can be used in the compiler IDE of choice. Cmake supports interactive and non-interactive modes to configure projects. It provides options to control code generation, set variables, and obtain help documentation for commands, modules, and other aspects of Cmake.
This document provides information on several API functions for working with directories, processes, memory, and file I/O in C/C++. It describes the ProcessIdToSessionId function which retrieves the Remote Desktop session associated with a process ID. It also describes the GetCurrentDirectory function which retrieves the current directory for the current process, and the SetCurrentDirectory function which sets the current directory. It provides details on memory functions like memset and file I/O functions like fread.
The document provides an overview of building Apache modules. It discusses Apache's request handling process, memory handling, and module architecture. The module architecture section describes how to structure an Apache module, including necessary includes, the module name, definition, commands (options), and configuration. It also covers registering hooks, initialization, creating new configuration directives, and logging.
Nginx uses an event-driven architecture with a master process that manages worker processes. It handles requests non-blockingly and efficiently using techniques like memory pooling, buffer chaining, and an event-driven model. Key parts of the architecture include phases and handlers for HTTP requests, virtual servers, locations, and filters. Nginx also supports mail proxying and module development.
This document provides instructions for installing and configuring the Squid proxy server on Linux. It discusses system requirements for disk performance and memory. It also covers downloading and installing Squid, important configuration notes, starting and stopping Squid, log files, configuring cache disks and directories, access control lists, authentication, and examples of restricting web access by time and to specific websites.
Using Apache as an Application Server allows building web applications with less effort by leveraging Apache's support for request processing, security, logging, and other services. The document discusses how Apache modules can integrate application services by running inside the Apache process and having access to the full HTTP request lifecycle. It provides an example Apache configuration and architecture for implementing a rule interpretation engine as an Apache module to deliver dynamic JavaScript for context-aware web pages.
Apache web server installation/configuration, Virtual Hostingwebhostingguy
The document describes the history and development of the Apache web server. Some key points:
- Apache was originally developed by the Apache group in 1995 as an open source alternative to NCSA httpd. It was called "A PAtCHy server" as it was initially developed through people contributing patch files to NCSA httpd.
- The first official public release was version 0.6.2 in April 1995. Key early features included adaptive pre-fork child processes and a modular/extensible structure and API.
- Apache quickly gained popularity and overtook NCSA httpd as the most widely used web server on the Internet after releasing version 1.0 in December 1995.
This document provides information about using the PHP command line interface (CLI) SAPI. It discusses when to use the CLI SAPI, such as for cron jobs, batch tasks, daemons, and process control. It also provides examples of using the PHP binary to execute scripts from the command line, pass arguments, read from STDIN, and use options like -a for interactive mode, -r to run PHP code directly, and -i to get PHP configuration information.
This document provides an overview of the Python web framework Flask. It discusses Flask's lightweight and extensible nature. It also covers key Flask concepts like URL routing, parameters, templates, and request handling. Examples are given for basic routing, parameter collection via GET and POST, and rendering templates with dynamic data. The document serves as an introduction to building web applications with the Flask framework in Python.
The document contains details of 10 practical assignments for a programming language course. It includes examples of code snippets to demonstrate inheritance, polymorphism, delegates, constructors, exception handling, file I/O, adding a flash item to a website, and explanations of XML and DTDs. The assignments cover core concepts of .NET framework and C# programming language.
This document summarizes options for running the Odoo server from the command line, including:
- Specifying database, modules, and module paths for installation/updating
- Configuring workers for multiprocessing and limiting resources per worker
- Setting logging options like the log file, database, or specific log levels
- Advanced options like auto-reloading or enabling a proxy
Thijs Feryn gave a presentation on the CLI (command line interface) SAPI for PHP. The CLI SAPI allows PHP scripts to be run from the command line/terminal instead of through a web server. Some key points of the CLI SAPI include reading arguments from $argv, reading input from STDIN, writing output to STDOUT, and having full control over script execution without timeouts. The CLI SAPI is useful for tasks like cronjobs, batch processing, and applications without a web frontend.
This document discusses various UNIX commands for processing text streams and filtering text, including cat, cut, head, tail, and split. It provides examples of using each command to select, modify, or restructure the output. The commands can be used to select parts of files like lines (head/tail) or columns (cut), and to split files into multiple parts (split). Pipelines and redirection are also covered.
This document provides a cheat sheet for using the UNIX C Shell, covering topics like file manipulation, terminal setup, changing directories, listing and displaying files, copying, moving, removing files, printing files, finding files, comparing files, setting permissions, input/output redirection, C shell specific commands, job control, and special startup files.
The document discusses various techniques for optimizing web program performance, including improving data structures and algorithms, reducing network, disk, and memory I/O, using NoSQL databases, optimizing frontend resource loading and execution, and testing and refactoring code for performance. It also covers specific optimizations related to caching, content delivery networks, domain name resolution, module loading, code packaging, and handling slower users.
"Building intuitive command-line interfaces in .NET", Alex ThissenFwdays
This document discusses CLIs (command line interfaces) and how they can be implemented in .NET. It provides an overview of the benefits of CLIs such as efficiency, automation, and cross-platform support. It then demonstrates how to build CLIs using .NET libraries like System.CommandLine, which provides object models for defining commands, arguments, options and handling command line parsing and execution. Features like middleware, error handling, suggestions and help are demonstrated. Best practices for CLIs like intuitiveness and discoverability are also covered.
The document discusses network programming and the client-server model. It begins with an overview of the client-server transaction process and the programmer's view of the Internet. It then covers topics like IP addresses, the Domain Name System (DNS), Internet connections using sockets, examples of clients and servers, and the sockets interface used for writing clients and servers.
This document provides an overview of a hands-on workshop on the Constrained Application Protocol (CoAP). It outlines the agenda which includes introductions to CoAP, the Californium CoAP framework, and hands-on projects. Attendees will work through example CoAP client and server code using the Californium libraries and test their implementations. Advanced CoAP topics like security, proxies, and resource directories are also discussed.
The document provides tips for optimizing PHP code, including using string functions instead of regular expressions where possible, passing references to reduce memory usage, using persistent database connections, and checking mysql_unbuffered_query() for faster queries. It also discusses HTTP requests and responses, cookie expiry, references in PHP, returning references from functions, and the debug_backtrace() function. The document concludes with tips for improving security such as checking for uninitialized variables, validating user input, and restricting access to included files.
Honeypots Unveiled: Proactive Defense Tactics for Cyber Security, Phoenix Sum...APNIC
Adli Wahid, Senior Internet Security Specialist at APNIC, delivered a presentation titled 'Honeypots Unveiled: Proactive Defense Tactics for Cyber Security' at the Phoenix Summit held in Dhaka, Bangladesh from 23 to 24 May 2024.
This document discusses the configuration of various server services, including:
- Setting up an Apache web server with SSL encryption and generating SSL certificates.
- Additional Apache configurations like virtual hosting, CGI scripts, and SELinux contexts.
- Basic SMTP configuration using Postfix and setting up an internal mail server.
- Configuring a caching-only DNS server using Named.
- Setting up NFS for file sharing between servers.
- Enabling file sharing with Windows clients using Samba (CIFS).
- Configuring an anonymous FTP server with vsftpd.
It provides instructions and examples for configuring each of these services on Linux servers.
Cmake is a cross-platform build system generator that allows users to specify platform-independent build processes. It generates native makefiles and workspaces that can be used in the compiler IDE of choice. Cmake supports interactive and non-interactive modes to configure projects. It provides options to control code generation, set variables, and obtain help documentation for commands, modules, and other aspects of Cmake.
This document provides information on several API functions for working with directories, processes, memory, and file I/O in C/C++. It describes the ProcessIdToSessionId function which retrieves the Remote Desktop session associated with a process ID. It also describes the GetCurrentDirectory function which retrieves the current directory for the current process, and the SetCurrentDirectory function which sets the current directory. It provides details on memory functions like memset and file I/O functions like fread.
The document provides an overview of building Apache modules. It discusses Apache's request handling process, memory handling, and module architecture. The module architecture section describes how to structure an Apache module, including necessary includes, the module name, definition, commands (options), and configuration. It also covers registering hooks, initialization, creating new configuration directives, and logging.
Nginx uses an event-driven architecture with a master process that manages worker processes. It handles requests non-blockingly and efficiently using techniques like memory pooling, buffer chaining, and an event-driven model. Key parts of the architecture include phases and handlers for HTTP requests, virtual servers, locations, and filters. Nginx also supports mail proxying and module development.
This document provides instructions for installing and configuring the Squid proxy server on Linux. It discusses system requirements for disk performance and memory. It also covers downloading and installing Squid, important configuration notes, starting and stopping Squid, log files, configuring cache disks and directories, access control lists, authentication, and examples of restricting web access by time and to specific websites.
Using Apache as an Application Server allows building web applications with less effort by leveraging Apache's support for request processing, security, logging, and other services. The document discusses how Apache modules can integrate application services by running inside the Apache process and having access to the full HTTP request lifecycle. It provides an example Apache configuration and architecture for implementing a rule interpretation engine as an Apache module to deliver dynamic JavaScript for context-aware web pages.
Apache web server installation/configuration, Virtual Hostingwebhostingguy
The document describes the history and development of the Apache web server. Some key points:
- Apache was originally developed by the Apache group in 1995 as an open source alternative to NCSA httpd. It was called "A PAtCHy server" as it was initially developed through people contributing patch files to NCSA httpd.
- The first official public release was version 0.6.2 in April 1995. Key early features included adaptive pre-fork child processes and a modular/extensible structure and API.
- Apache quickly gained popularity and overtook NCSA httpd as the most widely used web server on the Internet after releasing version 1.0 in December 1995.
This document provides information about using the PHP command line interface (CLI) SAPI. It discusses when to use the CLI SAPI, such as for cron jobs, batch tasks, daemons, and process control. It also provides examples of using the PHP binary to execute scripts from the command line, pass arguments, read from STDIN, and use options like -a for interactive mode, -r to run PHP code directly, and -i to get PHP configuration information.
This document provides an overview of the Python web framework Flask. It discusses Flask's lightweight and extensible nature. It also covers key Flask concepts like URL routing, parameters, templates, and request handling. Examples are given for basic routing, parameter collection via GET and POST, and rendering templates with dynamic data. The document serves as an introduction to building web applications with the Flask framework in Python.
The document contains details of 10 practical assignments for a programming language course. It includes examples of code snippets to demonstrate inheritance, polymorphism, delegates, constructors, exception handling, file I/O, adding a flash item to a website, and explanations of XML and DTDs. The assignments cover core concepts of .NET framework and C# programming language.
This document summarizes options for running the Odoo server from the command line, including:
- Specifying database, modules, and module paths for installation/updating
- Configuring workers for multiprocessing and limiting resources per worker
- Setting logging options like the log file, database, or specific log levels
- Advanced options like auto-reloading or enabling a proxy
Thijs Feryn gave a presentation on the CLI (command line interface) SAPI for PHP. The CLI SAPI allows PHP scripts to be run from the command line/terminal instead of through a web server. Some key points of the CLI SAPI include reading arguments from $argv, reading input from STDIN, writing output to STDOUT, and having full control over script execution without timeouts. The CLI SAPI is useful for tasks like cronjobs, batch processing, and applications without a web frontend.
This document discusses various UNIX commands for processing text streams and filtering text, including cat, cut, head, tail, and split. It provides examples of using each command to select, modify, or restructure the output. The commands can be used to select parts of files like lines (head/tail) or columns (cut), and to split files into multiple parts (split). Pipelines and redirection are also covered.
This document provides a cheat sheet for using the UNIX C Shell, covering topics like file manipulation, terminal setup, changing directories, listing and displaying files, copying, moving, removing files, printing files, finding files, comparing files, setting permissions, input/output redirection, C shell specific commands, job control, and special startup files.
The document discusses various techniques for optimizing web program performance, including improving data structures and algorithms, reducing network, disk, and memory I/O, using NoSQL databases, optimizing frontend resource loading and execution, and testing and refactoring code for performance. It also covers specific optimizations related to caching, content delivery networks, domain name resolution, module loading, code packaging, and handling slower users.
"Building intuitive command-line interfaces in .NET", Alex ThissenFwdays
This document discusses CLIs (command line interfaces) and how they can be implemented in .NET. It provides an overview of the benefits of CLIs such as efficiency, automation, and cross-platform support. It then demonstrates how to build CLIs using .NET libraries like System.CommandLine, which provides object models for defining commands, arguments, options and handling command line parsing and execution. Features like middleware, error handling, suggestions and help are demonstrated. Best practices for CLIs like intuitiveness and discoverability are also covered.
The document discusses network programming and the client-server model. It begins with an overview of the client-server transaction process and the programmer's view of the Internet. It then covers topics like IP addresses, the Domain Name System (DNS), Internet connections using sockets, examples of clients and servers, and the sockets interface used for writing clients and servers.
This document provides an overview of a hands-on workshop on the Constrained Application Protocol (CoAP). It outlines the agenda which includes introductions to CoAP, the Californium CoAP framework, and hands-on projects. Attendees will work through example CoAP client and server code using the Californium libraries and test their implementations. Advanced CoAP topics like security, proxies, and resource directories are also discussed.
The document provides tips for optimizing PHP code, including using string functions instead of regular expressions where possible, passing references to reduce memory usage, using persistent database connections, and checking mysql_unbuffered_query() for faster queries. It also discusses HTTP requests and responses, cookie expiry, references in PHP, returning references from functions, and the debug_backtrace() function. The document concludes with tips for improving security such as checking for uninitialized variables, validating user input, and restricting access to included files.
Honeypots Unveiled: Proactive Defense Tactics for Cyber Security, Phoenix Sum...APNIC
Adli Wahid, Senior Internet Security Specialist at APNIC, delivered a presentation titled 'Honeypots Unveiled: Proactive Defense Tactics for Cyber Security' at the Phoenix Summit held in Dhaka, Bangladesh from 23 to 24 May 2024.
Discover the benefits of outsourcing SEO to Indiadavidjhones387
"Discover the benefits of outsourcing SEO to India! From cost-effective services and expert professionals to round-the-clock work advantages, learn how your business can achieve digital success with Indian SEO solutions.
HijackLoader Evolution: Interactive Process HollowingDonato Onofri
CrowdStrike researchers have identified a HijackLoader (aka IDAT Loader) sample that employs sophisticated evasion techniques to enhance the complexity of the threat. HijackLoader, an increasingly popular tool among adversaries for deploying additional payloads and tooling, continues to evolve as its developers experiment and enhance its capabilities.
In their analysis of a recent HijackLoader sample, CrowdStrike researchers discovered new techniques designed to increase the defense evasion capabilities of the loader. The malware developer used a standard process hollowing technique coupled with an additional trigger that was activated by the parent process writing to a pipe. This new approach, called "Interactive Process Hollowing", has the potential to make defense evasion stealthier.
Securing BGP: Operational Strategies and Best Practices for Network Defenders...APNIC
Md. Zobair Khan,
Network Analyst and Technical Trainer at APNIC, presented 'Securing BGP: Operational Strategies and Best Practices for Network Defenders' at the Phoenix Summit held in Dhaka, Bangladesh from 23 to 24 May 2024.
1. Apache Quick Reference Card
Revision 1.6 for Apache version 1.3.6
This card summarizes information in the Apache documentation,
which can be found at http://www.apache.org/docs/.
Each directive is listed with its arguments. Defaults are given
where appropriate in parentheses at the end of the line, followed
by an indication of the status of the directive (C – core, B – base,
E – extension) and the contexts in which the directive is valid (c –
in a configuration file, v – within a virtual host section, d – within
a directory section, a – in an access control file).
Options and directives that are new for Apache 1.3 are marked 1.3,
while those that have changed are marked 1.3.
Command line options
httpd -d directory -f file -C directive
-c directive -L -l -S -v -V -X
-d directory initial value for ServerRoot
-D parameter define parameter for IfDefine
-f file configuration file (conf/httpd.conf)
-C directive process directive before reading config files 1.3
-c directive process directive after reading config files 1.3
-L list available configuration directives and exit 1.3
-l list compiled-in modules and exit 1.3
-S show vhost settings
-t test syntax of configuration files and exit
-v print version and build date, and exit
-V show compilation settings and exit 1.3
-X single-processs debug mode
General configuration directives
DocumentRoot directory (/usr/local/apache/htdocs)C cv
ServerRoot directory (/usr/local/apache)C c
AccessConfig filename (conf/access.conf)C cv
ResourceConfig filename (conf/srm.conf)C cv
Include filename C cvd 1.3
TypesConfig filename (conf/mime.types)B c
PidFile filename (logs/httpd.pid)C c
LockFile filename (logs/accept.lock)C c
ScoreBoardFile file (logs/apache_status)C c
ServerAdmin email-addr C cv
ServerType inetd standalone (standalone)C c
ServerName name (determined automatically) C cv
ServerAlias fqdn ... C v
ServerSignature On Off Email (Off) C cvda 1.3
ServerPath pathname C v
ServerTokens Minimal OS Full (Full)C c 1.3
BindAddress * IP-addr fqdn (*) C c
Listen IP-addr:port-number C c
Port portno (80) C c
User username #userid (#-1) C cv
Group group-name #group-id (#-1) C cv
NameVirtualHost addr:port C c 1.3
UseCanonicalName On Off (On) C cvda 1.3
CoreDumpDirectory directory (as ServerRoot)C c 1.3
IdentityCheck On Off (Off) C cvd
ClearModuleList C c
AddModule module ... C c
AddModuleInfo module text E cv 1.3
ExtendedStatus On Off (Off)E c 1.3
Sectional directives
Directory pattern ~ regex ... /Directory C cv 1.3
DirectoryMatch regex ... /DirectoryMatch C cv 1.3
Files pattern ~ regex ... /Files C cvda 1.3
FilesMatch regex ... /FilesMatch C cvda 1.3
Location pattern ~ regex ... /Location C cv 1.3
LocationMatch regex ... /LocationMatch C cv 1.3
VirtualHost pattern ... /VirtualHost C c
IfDefine !parameter ... /IfDefine C cvda 1.3
IfModule !module ... /IfModule C cvda
Limit method ... /Limit C cvda
LimitExcept method ... /LimitExcept C cvda
Logging directives
ErrorLog file syslog:facility (logs/error_log)C cv 1.3
CustomLog file-or-pipe format-string format-name
env=[!var]
B cv 1.3
TransferLog file-or-pipe (logs/access_log)B cv
HostnameLookups On Off Double (Off)C cvd 1.3
RefererIgnore hostname ... E cv
LogFormat format-string
format-name
(%h %l %u %t %r %s %b)B cv 1.3
LogLevel emerg alert crit error warn notice
info debug
(error)C cv 1.3
format-string can contain literal text and format specifiers:
%a Remote IP address
%b Number of bytes sent (excluding headers)
%{var}e Environment variable value
%f Filename
%h Remote host
%{hdr}i Incoming header value
%l Remote logname (from identd)
%{label}n Labelled note from another module 1.3
%{hdr}o Outgoing header value
%p Canonical port number of server
%P Process ID of child server process
%r First line of request
%s Status
%t Time in Common Log Format (CLF) format
%{format}t Time (format is strftime format)
%T Time taken to serve the request (in seconds)
%u Remote username
%U URL requested
%v Canonical ServerName of server
%V Server name as per UseCanonicalName setting 1.3
Performance tuning directives
Timeout secs (300) C c
KeepAlive On Off (On) C c
KeepAliveTimeout seconds (15) C c
MaxKeepAliveRequests number (100) C c
MaxClients number (256) C c
MaxRequestsPerChild number C c
ExcessRequestsPerChild number E c 1.3
MaxSpareServers number (10) C c
MinSpareServers number (5) C c
StartServers number (5) C c
ListenBacklog number (511) C c 1.3
LimitRequestBody nbytes C cvda 1.3
LimitRequestFields number (100) C c 1.3
LimitRequestFieldSize nbytes (8190) C c 1.3
LimitRequestLine nbytes (8190) C c 1.3
SendBufferSize bytes C c
RLimitCPU secs max secs max C cvda
RLimitMEM bytes max bytes max C cvda
RLimitNPROC nprocs max nprocs max C cvda
ThreadsPerChild number (50) C c 1.3
File typing directives
DefaultType MIME-type (text/html)C cvda
ForceType MIME-type B da
AddEncoding MIME-encoding extension ... B cvda
AddLanguage MIME-language extension ... B cvda
AddType MIME-type extension ... B cvda
DefaultLanguage MIME-language (no default language)C cvda 1.3
LanguagePriority MIME-language ... B cvda
XBitHack On Off Full (Off)B cvda
MetaFiles On Off (Off)E cvda 1.3
MetaDir dir-name (.web)E cvda 1.3
MetaSuffix suffix (.meta)E cvda 1.3
MimeMagicFile filename E cv 1.3
ContentDigest On Off (Off)C cvda
ExpiresActive On Off E cvda
ExpiresBytype MIME-type expiry-code E cvda
ExpiresDefault expiry-code E cvda
Header set append add unset header value E cvda
Mapping directives
Action MIME-type handler-name script B cvda
Alias url-path real-path B cv
AliasMatch url-regex path-replacement B cv 1.3
ErrorDocument error-code string url C cvda
UserDir directory DISABLED user ...
ENABLED user ...
(public_html)B cv 1.3
Redirect status url-path url B cvda
RedirectMatch status url-regex dest-url B cv 1.3
RedirectPermanent url-path url-dest B cvda
RedirectTemp url-path url-dest B cvda
Script method script B cvd
ScriptAlias url-path script-dir B cv
ScriptAliasMatch url-regex script-dir B cv 1.3
AddHandler handler-name extension ... B cvda
RemoveHandler extension ... B da 1.3
SetHandler handler-name B da
ImapBase map referer url (http://server)B cvda
ImapDefault error nocontent referer menu
url
(nocontent)B cvda
ImapMenu none formatted semiformatted unformatted B cvda
RewriteBase url E cvda
RewriteCond test-string cond-pattern flags E cvda
RewriteEngine On Off (Off)E cvda
RewriteLock filename E cv 1.3
RewriteLog filename E cv
RewriteLogLevel digit E cv
1 2 3
2. RewriteMap map-name map-type:map-source E cv 1.3
RewriteOptions option E cvda
RewriteRule pattern substitution flags E cvda 1.3
Scripting directives
BrowserMatch regexp var =value ... B cv
BrowserMatchNoCase regexp var =value ... B cv
PassEnv varname ... B cv
SetEnv varname value B cv
SetEnvIf attribute regex var =value ... B cv 1.3
SetEnvIfNoCase attribute regex var =value ... B cv 1.3
UnsetEnv varname ... B cv
ScriptLog filename B c
ScriptLogBuffer size-bytes (1024) B c
ScriptLogLength length-bytes (10385760) B c
Directory indexing directives
DirectoryIndex file ... (index.html)B cvda
ReadmeName filename B cvda
HeaderName filename B cvda
IndexIgnore pattern ... B cvda
IndexOrderDefault Ascending Descending Name Date
Size Description
B cvda 1.3
DefaultIcon url B cvda
AddAlt string file ... B cvda
AddAltByEncoding string MIME-encoding ... B cvda
AddAltByType string MIME-type ... B cvda
AddIcon icon file ... B cvda
AddIconByType icon MIME-type ... B cvda
AddIconByEncoding icon MIME-encoding ... B cvda
AddDescription description file-pattern B cvda
IndexOptions +option -option ... (no options) B cvda 1.3
Valid index options are: FancyIndexing,
IconsHeight=pixels, IconsWidth=pixels,
NameWidth=n, IconsAreLinks, ScanHTMLTitles,
SupressColumnSorting, SupressDescription,
SupressHTMLPreamble, SupressLastModified, SupressSize
Access control directives
AccessFileName filename ... (.htaccess)C cv 1.3
AllowOverride directive-group ... (All) C d
Valid directive groups are: None, All, AuthConfig, FileInfo,
Indexes, Limit, Options
Options +feature -feature ... (All) C cvda
Valid options are: None, All, ExecCGI, FollowSymLinks,
Includes, IncludesNOEXEC, Indexes, MultiViews,
SymLinksIfOwnerMatch
AuthName realm-name C da
AuthType type C da
AuthUserFile filename E da
AuthGroupFile filename E da
AuthAuthoritative On Off (On) B da
allow from all host ... env=var B da
deny from all host ... env=var B da
order allow,deny deny,allow
mutual-failure
(deny,allow)B da
Require user user ... group group ... valid-user C da
Satisfy All Any (All) C da
Proxy/cache directives
NoProxy host domain ip-addr subnet ... E cv 1.3
AllowCONNECT port ... (443 563)E cv 1.3
ProxyBlock * host domain ... E cv
ProxyDomain domain-name E cv 1.3
ProxyPass path url E cv
ProxyPassReverse path url E cv 1.3
ProxyReceiveBufferSize number-bytes E cv 1.3
ProxyRemote match remote-server E cv
ProxyRequests On Off (Off)E cv
ProxyVia On Off Full Block (Off)E cv 1.3
CacheDefaultExpire hours (1) E cv
CacheDirLength number (1) E cv
CacheDirLevels number (3) E cv
CacheForceCompletion percentage-complete (90) E cv 1.3
CacheGcInterval hours E cv
CacheLastModifiedFactor factor (0.1)E cv
CacheMaxExpire hours (24) E cv
CacheRoot directory E cv
CacheSize kb (5) E cv
NoCache * host domain ... E cv
Common Gateway Interface (CGI) variables
AUTH_TYPE Authentication method used
CONTENT_LENGTH Length of input stream data
CONTENT_TYPE Internet media type of input stream
GATEWAY_INTERFACE CGI version
PATH_INFO URL part after script identifier
PATH_TRANSLATED PATH_INFO translated into filesystem
QUERY_STRING Query string from URL (if present)
REMOTE_ADDR IP address of client
REMOTE_HOST DNS name of client
REMOTE_IDENT Remote user id (unreliable)
REMOTE_USER Name of the authenticated user
REQUEST_METHOD HTTP request method
SCRIPT_NAME Virtual path of the script
SERVER_NAME Host-name of the server
SERVER_PORT Port number of server
SERVER_PROTOCOL Name and version of the protocol
SERVER_SOFTWARE Server software name and version
HTTP_ACCEPT MIME types the browser will accept
HTTP_REFERER URL of referring document
HTTP_USER_AGENT Client software identification
MOD_PERL Defined if running under mod_perl
Server Side Includes (SSI)
Format is: !--#element attr=value ... --
Elements are:
config controls parsing; attributes: errmsg, sizefmt (one of
bytes or abbrev), timefmt (strftime format)
echo print the value of a variable; attribute var (can be
a CGI variable or one of: DATE_GMT, DATE_LOCAL,
DOCUMENT_NAME, DOCUMENT_URI or LAST_MODIFIED)
set set the value of a variable; attributes: var, value
printenv print a list of all variables and their values
exec execute a shell command or CGI script; attribute: cmd
or cgi (IncludesNOEXEC option disables exec)
fsize print size of file; attribute: file or virtual
flastmod print file modification time; attribute file or virtual
include include another document; attribute file or virtual
if conditional; attribute: expr
elif conditional; attribute: expr
else conditional
endif conditional
HTTP 1.1 status codes
100 Continue
101 Switching protocols
200 OK
201 Created
202 Accepted
203 Non-authoritative information
204 No content
205 Reset content
206 Partial content
300 Multiple choices
301 Moved permanently
302 Moved temporarily
303 See other
304 Not modified
305 Use proxy
400 Bad request
401 Unauthorized
402 Payment required
403 Forbidden
404 Not found
405 Method not allowed
406 Not acceptable
407 Proxy authentication required
408 Request timeout
409 Conflict
410 Gone
411 Length required
412 Precondition failed
413 Request entity too large
414 Request-URI too long
415 Unsupported media type
500 Internal server error
501 Not implemented
502 Bad gateway
503 Service unavailable
504 Gateway timeout
505 HTTP version not supported
Apache Web Resources
http://www.apache.org Apache home page
http://modules.apache.org Apache Module Registry
http://www.apache-ssl.org Apache-SSL home page
http://www.modssl.org mod ssl home page
http://java.apache.org The Java-Apache Project
http://perl.apache.org The Apache/Perl Integration Project
http://www.php.net PHP: Hypertext Processor
http://www.apacheweek.com Apache Week
http://www.netcraft.com/survey Netcraft Server Survey
http://www.refcards.com Quick Reference Cards
4 5 6