Facebook
Twitter-
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.
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