• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Question why static files end up in apache2 log?

epertinez

New Pleskian
Hi,
My server is not fast enough so I am trying to find ways to improve it.
One thing I don't get is that even when I have nginx set to act as proxy for static files, some of them get into apache2 log.
Can anybody tell me how is it possible?
Example:
access_ssl_log

<someIP> - - [28/Aug/2023:07:20:40 +0100] "GET <someURL>?gclid=<someGCLID> HTTP/1.0" 200 21593 "Enterprise Advertising & Analytics Solutions - Google Marketing Platform" "<someHttpUserAgent>"
<someIP> - - [28/Aug/2023:07:20:40 +0100] "GET <someURL>?gclid=<someGCLID> HTTP/1.0" 200 65783 "Enterprise Advertising & Analytics Solutions - Google Marketing Platform" "<someHttpUserAgent>"
<someIP> - - [28/Aug/2023:07:20:42 +0100] "GET /126011-someimage.jpg HTTP/1.0" 200 11068 "https://<someURL>?gclid=<someGCLID>" "<someHttpUserAgent>"
<someIP> - - [28/Aug/2023:07:20:42 +0100] "GET /132149-someimage.jpg HTTP/1.0" 200 65933 "https://<someURL>?gclid=<someGCLID>" "<someHttpUserAgent>"
<someIP> - - [28/Aug/2023:07:20:42 +0100] "GET /132149-someimage.jpg HTTP/1.0" 200 2641 "https://<someURL>?gclid=<someGCLID>" "<someHttpUserAgent>"
<someIP> - - [28/Aug/2023:07:20:42 +0100] "GET /132153-someimage.jpg HTTP/1.0" 200 6817 "https://<someURL>?gclid=<someGCLID>" "<someHttpUserAgent>"
<someIP> - - [28/Aug/2023:07:20:42 +0100] "GET /132168-someimage.jpg HTTP/1.0" 200 3597 "https://<someURL>?gclid=<someGCLID>" "<someHttpUserAgent>"
<someIP> - - [28/Aug/2023:07:20:42 +0100] "GET /134849-someimage.jpg HTTP/1.0" 200 11838 "https://<someURL>?gclid=<someGCLID>" "<someHttpUserAgent>"
<someIP> - - [28/Aug/2023:07:20:42 +0100] "GET /135337-someimage.jpg HTTP/1.0" 200 9181 "https://<someURL>?gclid=<someGCLID>" "<someHttpUserAgent>"
<someIP> - - [28/Aug/2023:07:20:42 +0100] "GET /138484-someimage.jpg HTTP/1.0" 200 10117 "https://<someURL>?gclid=<someGCLID>" "<someHttpUserAgent>"
<someIP> - - [28/Aug/2023:07:20:42 +0100] "GET /150762-someimage.jpg HTTP/1.0" 200 20013 "https://<someURL>?gclid=<someGCLID>" "<someHttpUserAgent>"
<someIP> - - [28/Aug/2023:07:20:42 +0100] "GET /29089-someimage.jpg HTTP/1.0" 200 10930 "https://<someURL>?gclid=<someGCLID>" "<someHttpUserAgent>"
<someIP> - - [28/Aug/2023:07:20:42 +0100] "GET /29331-someimage.jpg HTTP/1.0" 200 12272 "https://<someURL>?gclid=<someGCLID>" "<someHttpUserAgent>"

<someIP> - - [28/Aug/2023:07:20:42 +0100] "GET /82807-someimage.jpg HTTP/1.0" 200 5099 "https://<someURL>?gclid=<someGCLID>" "<someHttpUserAgent>"



while proxy_access_ssl_log is also serving some other static files. jpg included to the same ip (in this case using http/2.0.

In this case, lots of svg are served by nginx, but in other cases those are served with apache2. And using http/2.0. So... I don't know what is going on.
 
Back
Top