Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

getTrace() in FireLogger causes bad gateway #267

Closed
adrianbj opened this issue Oct 18, 2017 · 3 comments
Closed

getTrace() in FireLogger causes bad gateway #267

adrianbj opened this issue Oct 18, 2017 · 3 comments

Comments

@adrianbj
Copy link
Contributor

@adrianbj adrianbj commented Oct 18, 2017

  • bug report? probably not
  • feature request? not sure :)
  • version: 2.4.10

Description

I have a site running on nginx that returns a 502 bad gateway from the $trace = $e->getTrace(); statement in FireLogger.php.

The actual error is:

upstream sent too big header while reading response header from upstream

If I change it to use getTraceAsString, everything works fine. Obviously this is not a solution though as we need the array of results. I know I can set fastcgi_buffers and fastcgi_buffer_size to higher values and it should be able to prevent this, but I am surprised that the getTrace() call in Bluescreen/content.phtml is not causing the same problem. Maybe one is sent through headers and the other through body which is why nginx isn't complaining on the Bluescreen call?

Just throwing this out there to see if you might have a solution - thanks.

@adrianbj

This comment has been minimized.

Copy link
Contributor Author

@adrianbj adrianbj commented Oct 18, 2017

Just looking at this a little more and obviously it is the header vs body issue because communicating with FireLogger is done through the header.

Maybe there isn't really a way to avoid this problem other than to change the fastcgi_buffers settings.

In case you're on a server where you don't have access to do this, I wonder if it might be possible to have a new option to disable FireLogger completely? Is this something you'd be willing to implement? Maybe:

Debugger::$disableFireLogger = true;
@adrianbj

This comment has been minimized.

Copy link
Contributor Author

@adrianbj adrianbj commented Mar 15, 2018

Hi @dg - can I bump this one please. I am working a on couple of sites where I can't adjust the fastcgi_buffers and fastcgi_buffer_size

Because I have https://github.com/MattSkala/chrome-firelogger installed on Chrome I really need a way to disable everything in Firelogger.php - is this something you might consider adding as a config option?

Thanks.

@dg dg closed this in a96df2d Mar 18, 2018
@adrianbj

This comment has been minimized.

Copy link
Contributor Author

@adrianbj adrianbj commented Mar 18, 2018

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.