Shulou(Shulou.com)06/02 Report--

Preface

As you all know, nginx has a powerful logging function, but by default, it can only record the user's IP address and browser information. What if we have a user logging in to the registration system and want to record which user is visiting a certain web page if the user is already logged in? Because we not only want to know which IP address visited which web page, but also want to know which login user visited which web page, which is very useful for us to recommend information or even push ads to him or her in the future. Without saying much, let's take a look at the detailed introduction:

Default log format for nginx

127.0.0.1-[20/Jul/2017:22:04:08 + 0800] "GET / news/index HTTP/1.1" 22262 "-" Mozilla/5.0 (Macintosh; Intel Mac OS X 10 / 12 / 5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.66 Safari/537.36 "

Here, we see that although the user has logged in, there is no information related to the user in the log, only the ip address. What if we want to record the user's id and other information?

Output a special header on the PHP side

We thought that now that the user has logged in, it must have cookie or session or token information, either way, our php must be able to effectively get this user's information. For example, we get the user's id information through session:

$user_id = Yii::$app- > session ['user_id']; if (empty ($user_id)) {header (' X-UID: 0');} else {header ('X-UID:'. $user_id);}

If there is no user id in session, the user is not logged in yet, and output X-UID: 0 (or you can output nothing at all). If we get the session, which means the user is logged in, we output his user_id to the form nginx: X-UID: 12345.

Here, you can output more than one message, you can output several different fields, including his name, gender, age, and so on.

Create a new log format

The log_format can only be stored in the http segment, so we need to find the nginx.conf file.

The second part of nginx's default log format is user information, but usually nothing but a-- here we transform it into header information that we pass in from the back end. The special header we created above is X-UID. Here, you need to do a small conversion, change all uppercase letters to lowercase, change all-to underscore, become x_uid, and then concatenate $upstream_http_ in front to get the final result $upstream_http_x_uid, and then insert it into the log format wherever you want it to appear:

Log_format front'$remote_addr-$upstream_http_x_uid [$time_local] "$request" $status $body_bytes_sent "$http_referer"$http_user_agent"'

Refer to this log format in server

In the server-related settings, because we named the log format front above, when we refer to it here, we need to specify the front log format:

Access_log / var/log/nginx/front-access.log front

New log results

127.0.0.1-52248 [20/Jul/2017:22:35:40 + 0800] "GET / news/view?id=56 HTTP/1.1" 19455 "-" Mozilla/5.0 (Macintosh; Intel Mac OS X 10 / 12 / 5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.66 Safari/537.36 "

Note: the second number above is 52248, which is the personal ID of our logged-in user. My example here is relatively simple, if you don't mind the trouble, you can even print all the personal information of the logged-in user, including your mobile phone number and mailbox, in the log, depending on whether you are concerned about security.

Hide id from users

In the first step above, we output a special header using php. Originally, our header is only for nginx expenses, but this header will be displayed to the front end intact by nginx, and careful users may feel uneasy. To do this, we can add a small switch to the server setting of nginx to hide the header:

Proxy_hide_header X-UID

In this way, the user will not be able to see this special header from the browser side, and it does not affect the nginx to record it.

Final treatment

So what's the use of recording an ID with so much effort? This will be of great use. As we all know, we have a powerful tool for log analysis, logstash, which can be combined with ELK components to analyze and deal with Apache or nginx logs. If we don't have this ID information, at most we can only figure out which web page is frequently visited by users, that's all. But now that we have the user ID, we can even connect to the mysql database table for analysis to study which age group, which gender, or which city users like to visit what web page, or even targeted to understand a specific user, he likes to visit what web page, and then targeted to provide him with customized services. Isn't that strong enough?

Summary

The above is the whole content of this article, I hope that the content of this article can bring some help to your study or work, if you have any questions, you can leave a message and exchange, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.