Difference between revisions of "Apache Basics and simple CGI scripts"
(→Appache Configuration) |
(→Motivation) |
||
| Line 5: | Line 5: | ||
The web is ubiquitous today. Everything comes with built-in web servers and there are many free/open source web-servers available. For a long time '''Apache''' was the most used web server and it is still rather prominent today. It has recently been surpassed by '''nginx'''<ref>https://news.netcraft.com/archives/category/web-server-survey/</ref> (pronounced: ''engine-x''). Still the versatility of Apache and the time-tested security makes it a good choice for many applications. |
The web is ubiquitous today. Everything comes with built-in web servers and there are many free/open source web-servers available. For a long time '''Apache''' was the most used web server and it is still rather prominent today. It has recently been surpassed by '''nginx'''<ref>https://news.netcraft.com/archives/category/web-server-survey/</ref> (pronounced: ''engine-x''). Still the versatility of Apache and the time-tested security makes it a good choice for many applications. |
||
| − | Here you will learn the basics to get you started with running an apache web server |
+ | Here you will learn the basics to get you started with running an apache web server, yet many of the concepts will apply to any web server. |
== Appache Configuration == |
== Appache Configuration == |
||
Revision as of 17:52, 31 March 2020
Motivation
The web is ubiquitous today. Everything comes with built-in web servers and there are many free/open source web-servers available. For a long time Apache was the most used web server and it is still rather prominent today. It has recently been surpassed by nginx[1] (pronounced: engine-x). Still the versatility of Apache and the time-tested security makes it a good choice for many applications.
Here you will learn the basics to get you started with running an apache web server, yet many of the concepts will apply to any web server.
Appache Configuration
Virtual Web Servers
A web server without encryption answers on port 80. If you have https encryption then it answers on port 443. If you have more then one IP you can choose which IP address the socket binds
to.
When a web client connect they will ask for the URI part (the part behind the host name) but after the request the host name that should be sent is also transmitted (in http/1.1 requests). Thus the server can present different web pages depending on the host name.
So the server can discern what the client wants, either be the IP address and/or by the host name that the client requested. So we speak of IP-based and name-based virtual hosts.
