• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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