Thank you@guillbdx.

Nice! This was the one thing missing from the new testing assertions. Thanks for working on this.

I'm getting an nginx error caused by a too large X-Debug-Exception header (upstream sent too big header while reading response header from upstream). This happens with a moderately large exception text (few kilobytes) and default nginx fastcgi buffer size settings. Is there any way to disable the X-Debug-Exception header population without disabling Symfony's debug mode altogether?

Hello@eng1neer and thank you for reaching out.

This tracker is meant for tracking bugs and feature requests. If you are looking for support, you'll get faster responses by using one of our official support channels:

• StackOverflow:https://stackoverflow.com/questions/tagged/symfony
• Slack:https://symfony.com/slack

Seehttps://symfony.com/support for more support options.

Hey,@derrabus thanks for taking the time to flag my message as off-topic.

I would argue that this is actually a bug. Stuffing data of an arbitrary length into HTTP headers is a bad idea. Most of the web servers impose a limit on the amount of data that can be transmitted in HTTP headers and this limit is not too big (4-8KB for Apache or Nginx). You can easily exceed it with a few kilobytes of text in the exception message which leads to an unexpected error page generated by the webserver.

There should be other, more appropriate ways to pass exception information in tests that will not intervene with the usual development workflow.

@eng1neer All right then, please file a bug report.