Now that we know about Web server logs, we can talk about Web server software.
The first Web server we will review will be Apache.
Apache is an open source Web server software that's maintained by the Apache Foundation.
The different locations of logs and Linux and Windows can be seen here.
Http. D dot com is the file where you can set the logs configuration, including the logs format.
This right here is the default log format.
You can find more details on the Apache Web page.
Now Let's try and understand the log fields on the Web on the Apache Web server log.
Here we have all the key fields client type RFC 1413 User I d Dating, Time method and so on.
It's the same format as the previous example, but with different values on the fields.
the hyphen means no information for that field.
let's analyze these next to log lines
to answer our questions of who, when and what will use this table to help us identify the key fields.
Here are the results for the first line
all the key fields are present.
Now let me show you the results for the second line.
We now have the answer for who, when and what. And in addition, we have the refer and the user agent.
After reviewing the Apache Web server, let's talk about N G i n X locks.
N G I N X is very similar to Apache.
Here is the default location of its logs.
Also, the default configuration for Engine X includes logging.
N G I. N X contains the law configuration for both Linux and Windows, including the log format.
Now let's try and understand this next n g i N X logline.
Ah, good thing is N G I N X logs Look a lot like the Apache logs.
Basically, we have the same fields. Client I P R F c. 14113 User i d Dating Time Method requested file. Http version and so on.
However, despite the two looking similar, it's always better to just practice. So let's analyze the two lines of log from N G i N X.
Here, the result of the first line is followed by the refer and user agent.
the hyphen means no information for that field. So in this line, we don't have the refer
here is the result for the second line with the refer and user agent.
Now we can answer the who when and what
our next Web server will be. Microsoft I I s
Microsoft. I s is a little different from the other two, but this won't be a problem.
Here is the default log location.
Other Web server configurations, including logging, are made on the I s manager a graphical user interface.
Just to note the log options for I s will look like this.
Even if the log looks a little different, it should contain all the needed log fields.
Let's try to understand the ice locks
here. We have an example of an IIS log.
First, we have the date and time.
Next is the Web server I P. Address followed by the http method
We have the requested file followed by a specific space for you are I Query.
The server port is 80. So it should be an http request,
remember, 80 is common to http and 443 is common to https.
Next, the user name, which is the same as user ID
client I p address user agent
Windows related field and the time taken to answer the request.
We have many fields, right? But more importantly, we have all the needed fields.
Now let's analyze two lines of log from I I s
We need to change our table just a little bit
building on the table. We see the result
not so different from Apache and Giant X.
If you want to try positive video answer.
Here are the results of the second line.
One of the differences is the server port.
It is possible to add this field in Apache and N G and X. It's also possible to have two different log lines one to TCP Port 80 and another to TCP four. Port 443
Now, I'd like to point out that access log files are not the only log files that could be used to analyze the Web server. There are other log files.
One good example is the error log file.
It's like debugging information.
All Web server software contains an error log file.
Here's some examples of locations for N, G, i N X, Apache and I. I s
check the Web server page to look for more information about error locks.
Here is the address for the error log in Apache.
To make things more clear, here are two logs from the Web server.
The first is an error log in the second is related access log.
Both logs were generated by the same request.
The access log line will have the client request, and the air logline will have the debug information for the request.
You can find similar information in both logs, like Client I P. Address the requested file and the method.
If you don't have enough information from the access log, you can always look for the error log.
And it could be really helpful when doing analysis
for the first post assessment question.
Which fields below are examples of key information provided by Web server logs.
You can pause the video if you'd like.
The answer is A, C, E and G.
Here are the descriptions of each option.
The next question. Extract the key information from the logs below and fill in the table.
Here you have the answer, and you can see our questions.
In addition, it's important to identify which Web server generated these locks.
The first law is from I s
The second one. Looks like a log from Apache or N G I N X.
To solve this question, it's better to ask the server admin.
In this case, the log is from an N g i n X Server.
It's common for a company to have many different types of Web servers
in the same company you confined Apache and G and X and I. I s.
That's why it's important to know many Web server options,
even if the software is different. You're looking for the same information
In this video, we started defining what logs are and why they're important.
Afterwards, we explain the fields for the Web application or Web server log.
Finally, we went through Apache Engine X and I s logs to learn how to get the key information in the log fields.
And finally we discussed airlocks and how they can help us with log analysis.
you'll see some consideration about log analysis. We'll talk about fake requests, the differences between knock and sock analysis, and we'll discuss the mistakes that can occur during Weblog analysis