Tom

Hi all, Does anybody having an implementation of awstats on IIS webserver behind a proxy running? We receive the real user IP in X-Forwarded-For and not c-ip - field. #Fields: date time s-sitename s-computername s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs-version cs(User-Agent) cs(Cookie) cs(Referer) cs-host sc-status sc-substatus sc-win32-status sc-bytes cs-bytes time-taken X-Forwarded-For 2022-05-25 00:05:43 W3SVC2 www 10.0.1.30 HEAD / - 443 - 10.0.1.10 HTTP/1.0 Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64;+rv:66.0)+Gecko/20100101+Firefox/66.0...

I was not able to use a custom logformat, because the IIS logs do have somewhere in the middle some commented out lines. AWStats did not find any valid log lines that match your LogFormat parameter, in the 50th first non commented lines read of your log. Your log file type C:\Windows\System32\LogFiles\W3SVC2\*.log | must have a bad format or LogFormat parameter setup does not match this format. Your AWStats LogFormat parameter is: %time2 %other %other %other %method %url %query %other %other %other...

Hi all, I wrote a small tool on .NET 4.5.2 to replace the value of cs-ip with the value of x-forwarded-for within the IIS logfiles. The x-forwarded-for column will be removed completetly at the end. After the processing i have IIS logs as if there is no reverse proxy in front of IIS. awstat can then process the logs without any problems. It works good for me. Questions? Just hit me up. Best regards, Tom

Hi all, I wrote a small tool on .NET 4.5.2 to replace the value of cs-ip with the value of x-forwarded-for within the IIS logfiles. The x-forwarded-for column will be removed completetly at the end. After the processing i have IIS logs as if there is no reverse proxy in front of IIS. awstat can then process the logs without any problems. It works good for me. Questions? Just hit me up. Best regards, Tom

Hi all, I wrote a small tool on .NET 4.5.2 to replace the value of cs-ip with the value of x-forwarded-for within the IIS logfiles. The x-forwarded-for column will be removed completetly at the end. After the processing i have IIS logs as if there is no reverse proxy in front of IIS. awstat can then process the logs without any problems. It works good for me. Questions? Just hit me up. Best regards, Tom

I was not able to use a custom logformat, because the IIS logs do have somewhere in the middle some commented out lines. AWStats did not find any valid log lines that match your LogFormat parameter, in the 50th first non commented lines read of your log. Your log file type C:\Windows\System32\LogFiles\W3SVC2\*.log | must have a bad format or LogFormat parameter setup does not match this format. Your AWStats LogFormat parameter is: %time2 %other %other %other %method %url %query %other %other %other...

Hi all, Does anybody having an implementation of awstats on IIS webserver behind a proxy running? We receive the real user IP in X-Forwarded-For and not cs-ip - field. #Fields: date time s-sitename s-computername s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs-version cs(User-Agent) cs(Cookie) cs(Referer) cs-host sc-status sc-substatus sc-win32-status sc-bytes cs-bytes time-taken X-Forwarded-For 2022-05-25 00:05:43 W3SVC2 www 10.0.1.30 HEAD / - 443 - 10.0.1.10 HTTP/1.0 Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64;+rv:66.0)+Gecko/20100101+Firefox/66.0...

/ipfilter parameter