{
	"id": "2a19c7e4-32ab-4972-af52-893eb383b964",
	"created_at": "2026-04-06T01:29:53.183105Z",
	"updated_at": "2026-04-10T03:20:41.643116Z",
	"deleted_at": null,
	"sha1_hash": "1f2e040958df764a4137bd25a5c8e86dfbd480b0",
	"title": "Apache HTTP Server Version 2.4",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 133526,
	"plain_text": "Apache HTTP Server Version 2.4\r\nArchived: 2026-04-06 01:26:18 UTC\r\nGetting Started\r\nAvailable Languages:  en  |  fr  |  ru \r\nIf you're completely new to the Apache HTTP Server, or even to running a website at all, you might not know\r\nwhere to start, or what questions to ask. This document walks you through the basics.\r\nSee also\r\nComments\r\nClients, Servers, and URLs\r\nAddresses on the Web are expressed with URLs - Uniform Resource Locators - which specify a protocol (e.g.\r\nhttp ), a servername (e.g. www.apache.org ), a URL-path (e.g. /docs/current/getting-started.html ), and\r\npossibly a query string (e.g. ?arg=value ) used to pass additional arguments to the server.\r\nA client (e.g., a web browser) connects to a server (e.g., your Apache HTTP Server), with the specified protocol,\r\nand makes a request for a resource using the URL-path.\r\nhttp://httpd.apache.org/docs/2.4/getting-started.html#content\r\nPage 1 of 4\n\nThe URL-path may represent any number of things on the server. It may be a file (like getting-started.html ) a\r\nhandler (like server-status) or some kind of program file (like index.php ). We'll discuss this more below in the\r\nWeb Site Content section.\r\nThe server will send a response consisting of a status code and, optionally, a response body. The status code\r\nindicates whether the request was successful, and, if not, what kind of error condition there was. This tells the\r\nclient what it should do with the response. You can read about the possible response codes in HTTP Server wiki.\r\nDetails of the transaction, and any error conditions, are written to log files. This is discussed in greater detail\r\nbelow in the Logs Files and Troubleshooting section.\r\nHostnames and DNS\r\nIn order to connect to a server, the client will first have to resolve the servername to an IP address - the location on\r\nthe Internet where the server resides. Thus, in order for your web server to be reachable, it is necessary that the\r\nservername be in DNS.\r\nIf you don't know how to do this, you'll need to contact your network administrator, or Internet service provider, to\r\nperform this step for you.\r\nMore than one hostname may point to the same IP address, and more than one IP address can be attached to the\r\nsame physical server. Thus, you can run more than one web site on the same physical server, using a feature called\r\nvirtual hosts.\r\nIf you are testing a server that is not Internet-accessible, you can put host names in your hosts file in order to do\r\nlocal resolution. For example, you might want to put a record in your hosts file to map a request for\r\nwww.example.com to your local system, for testing purposes. This entry would look like:\r\n127.0.0.1 www.example.com\r\nA hosts file will probably be located at /etc/hosts or C:\\Windows\\system32\\drivers\\etc\\hosts .\r\nYou can read more about the hosts file at Wikipedia.org/wiki/Hosts_(file), and more about DNS at\r\nWikipedia.org/wiki/Domain_Name_System.\r\nConfiguration Files and Directives\r\nThe Apache HTTP Server is configured via simple text files. These files may be located any of a variety of places,\r\ndepending on how exactly you installed the server. Common locations for these files may be found in the httpd\r\nwiki. If you installed httpd from source, the default location of the configuration files is\r\n/usr/local/apache2/conf . The default configuration file is usually called httpd.conf . This, too, can vary in\r\nthird-party distributions of the server.\r\nhttp://httpd.apache.org/docs/2.4/getting-started.html#content\r\nPage 2 of 4\n\nThe configuration is frequently broken into multiple smaller files, for ease of management. These files are loaded\r\nvia the Include directive. The names or locations of these sub-files are not magical, and may vary greatly from\r\none installation to another. Arrange and subdivide these files as makes the most sense to you. If the file\r\narrangement you have by default doesn't make sense to you, feel free to rearrange it.\r\nThe server is configured by placing configuration directives in these configuration files. A directive is a keyword\r\nfollowed by one or more arguments that set its value.\r\nThe question of \"Where should I put that directive?\" is generally answered by considering where you want a\r\ndirective to be effective. If it is a global setting, it should appear in the configuration file, outside of any\r\n\u003cDirectory\u003e , \u003cLocation\u003e , \u003cVirtualHost\u003e , or other section. If it is to apply only to a particular directory, then\r\nit should go inside a \u003cDirectory\u003e section referring to that directory, and so on. See the Configuration Sections\r\ndocument for further discussion of these sections.\r\nIn addition to the main configuration files, certain directives may go in .htaccess files located in the content\r\ndirectories. .htaccess files are primarily for people who do not have access to the main server configuration\r\nfile(s). You can read more about .htaccess files in the .htaccess howto.\r\nWeb Site Content\r\nWeb site content can take many different forms, but may be broadly divided into static and dynamic content.\r\nStatic content is things like HTML files, image files, CSS files, and other files that reside in the filesystem. The\r\nDocumentRoot directive specifies where in your filesystem you should place these files. This directive is either\r\nset globally, or per virtual host. Look in your configuration file(s) to determine how this is set for your server.\r\nTypically, a document called index.html will be served when a directory is requested without a file name being\r\nspecified. For example, if DocumentRoot is set to /var/www/html and a request is made for\r\nhttp://www.example.com/work/ , the file /var/www/html/work/index.html will be served to the client.\r\nDynamic content is anything that is generated at request time, and may change from one request to another. There\r\nare numerous ways that dynamic content may be generated. Various handlers are available to generate content.\r\nCGI programs may be written to generate content for your site.\r\nThird-party modules like mod_php may be used to write code that does a variety of things. Many third-party\r\napplications, written using a variety of languages and tools, are available for download and installation on your\r\nApache HTTP Server. Support of these third-party things is beyond the scope of this documentation, and you\r\nshould find their documentation or other support forums to answer your questions about them.\r\nLog Files and Troubleshooting\r\nhttp://httpd.apache.org/docs/2.4/getting-started.html#content\r\nPage 3 of 4\n\nAs an Apache HTTP Server administrator, your most valuable assets are the log files, and, in particular, the error\r\nlog. Troubleshooting any problem without the error log is like driving with your eyes closed.\r\nThe location of the error log is defined by the ErrorLog directive, which may be set globally, or per virtual host.\r\nEntries in the error log tell you what went wrong, and when. They often also tell you how to fix it. Each error log\r\nmessage contains an error code, which you can search for online for even more detailed descriptions of how to\r\naddress the problem. You can also configure your error log to contain a log ID which you can then correlate to an\r\naccess log entry, so that you can determine what request caused the error condition.\r\nYou can read more about logging in the logs documentation.\r\nSource: http://httpd.apache.org/docs/2.4/getting-started.html#content\r\nhttp://httpd.apache.org/docs/2.4/getting-started.html#content\r\nPage 4 of 4",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"references": [
		"http://httpd.apache.org/docs/2.4/getting-started.html#content"
	],
	"report_names": [
		"getting-started.html#content"
	],
	"threat_actors": [],
	"ts_created_at": 1775438993,
	"ts_updated_at": 1775791241,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/1f2e040958df764a4137bd25a5c8e86dfbd480b0.pdf",
		"text": "https://archive.orkl.eu/1f2e040958df764a4137bd25a5c8e86dfbd480b0.txt",
		"img": "https://archive.orkl.eu/1f2e040958df764a4137bd25a5c8e86dfbd480b0.jpg"
	}
}