• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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