• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Logformat

Frater

Regular Pleskian
I am considering to use a reverse-proxy for http on the system where Plesk is installed.

When I do I will need to use a different 'LogFormat=' in Apache because all traffic will otherwise be logged as coming from the proxy (the same IP as the server)

This is working on a normal Apache config...

/etc/apache2/conf.d/proxy:

SetEnvIf X-Forwarded-For "^.*\..*\..*\..*" is-forwarder

LogFormat "%h %v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_non_proxy
LogFormat "%{X-Forwarded-For}i %v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_proxy

/etc/apache2/sites-available/default:
CustomLog /var/log/apache2/access.log vhost_proxy env=is-forwarder
CustomLog /var/log/apache2/access.log vhost_non_proxy env=!is-forwarder

It now seems each site has their own customlog....
What's the most elegant solution to make Plesk reverse-proxy aware?

I wouldn't mind a solution where both IP's are logged (otherwise I wouldn't get the IP of a foreign proxy in case the reverse proxy on the local machine is turned off). But I think this will confuse some statistics scripts....
 
Back
Top