-
Notifications
You must be signed in to change notification settings - Fork 462
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
traffic stats bug (proxy_cache_valid) #8
Comments
It seems like normal situation because the proxy_cache is enabled, probably next requests would be sent from cache after processed one request. |
You can check for yourself by comparing the log traffic statistics on pure Nginx and modulet and you will be surprised that no module written to the log data is correct and enabled module, you will see that the server sends a response 304 but he writes in the log is not the correct data transferred bytes |
Please explain the situation in detail.(Your link is not an english)
|
OK, test config to example.com -> proxy -> backendlog_format bbs '$status | server_name:$server_name | body_bytes_sent:$body_bytes_sent | cache_status:$upstream_cache_status'; server { upstream backend { server 127.0.0.1:8888; } server { server { server { make 3 request log (bbs) 200 | server_name:example.com | body_bytes_sent:1048576 | cache_status:HIT 304 | server_name:backend | body_bytes_sent:0 | cache_status:- in log all good, but if we look at what we show module, we see incorrect data |
The request(yours) is processed as follows:
The module(vts) is processed as follows: In step2 is using step1's result(status_code, in_bytes, out_bytes...) At this moment in time, the nginx-module-vts is using the server context's result for the upstream context's result. |
Hi.
not counting the correct use of traffic statistics at proxy_cache_valid, the problem is shown here http://forum.nginx.org/read.php?21,257971
The text was updated successfully, but these errors were encountered: