Welcome! Log In Create A New Profile

Advanced

Re: error log truncates important infos

June 15, 2016 09:51AM
Hmm I understand that limitation. But an attacker or a bad application can hide the important information which we need to identify the source of the problem.

What about limiting the fastcgi output to 1024 bytes and appending this info with max 1024 bytes.
client: 127.0.0.1, server: example.com, upstream: "fastcgi://unix:/var/run/php-fpm-example.com.sock:", host: "127.0.0.1" , request: "GET / HTTP/1.1"

[fastcgi - output max 1024][request info: client, server, upstream, host, request - max 1024]

This would ensure that client, server and upstream are always provided. Host and Request can be filled with "user generated" content, so you should put it to the end. This would ensure that an attacker cannot hide the important fields.
Subject Author Posted

error log truncates important infos

philipp June 14, 2016 10:44AM

Re: error log truncates important infos

Robert Paprocki June 14, 2016 10:54AM

Re: error log truncates important infos

Maxim Dounin June 14, 2016 11:12AM

Re: error log truncates important infos

philipp June 15, 2016 09:51AM

Re: error log truncates important infos

Robert Paprocki June 15, 2016 11:56AM

Re: error log truncates important infos

B.R. June 15, 2016 01:24PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 332
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 500 on July 15, 2024
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready