Facebook
Twitter-
Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
To get into the festive spirit, install the Skins extension. -
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.
How to control stats in access_log
- Thread starter mikemcc
- Start date
Thanks IgorG.
I'm not a professional coder (just a businessman) but I developed a menuing system so customers can browse and screen video. I used php and MySQL. Mainly a prompt screen calls a processing script, passing a couple of parameters.
My access.log seems to contain mainly GET or POST for the parameters or for the graphics used to brighten up the menus.
In many log entries there are codes like "200 6002" and I can't find any documentation which lists these codes so the entries don't seem very interesting. Do you know of any documentation which helps interpret the log file ?
I can't work out whether and where I can stifle useless messages at source eg in PHP code or Apache parameters.
I suspect that if I can suppress useless log entries, I won't need a stats package to analyze the remaining ones.
Thanks again.
Mike
I'm not a professional coder (just a businessman) but I developed a menuing system so customers can browse and screen video. I used php and MySQL. Mainly a prompt screen calls a processing script, passing a couple of parameters.
My access.log seems to contain mainly GET or POST for the parameters or for the graphics used to brighten up the menus.
In many log entries there are codes like "200 6002" and I can't find any documentation which lists these codes so the entries don't seem very interesting. Do you know of any documentation which helps interpret the log file ?
I can't work out whether and where I can stifle useless messages at source eg in PHP code or Apache parameters.
I suspect that if I can suppress useless log entries, I won't need a stats package to analyze the remaining ones.
Thanks again.
Mike
Similar threads
