Commit e6775d74 authored by Fabien Potencier's avatar Fabien Potencier

fixed docs

parent 684812b6
...@@ -516,12 +516,20 @@ setting a more specific type hint for the Closure argument:: ...@@ -516,12 +516,20 @@ setting a more specific type hint for the Closure argument::
As Silex ensures that the Response status code is set to the most As Silex ensures that the Response status code is set to the most
appropriate one depending on the exception, setting the status on the appropriate one depending on the exception, setting the status on the
response alone won't work. If you want to overwrite the status code response alone won't work.
of the exception response, which you should not without a good reason, call
If you want to overwrite the status code, which you should not without a
good reason, set the ``X-Status-Code`` header (on Symfony until version
3.2)::
return new Response('Error', 404 /* ignored */, array('X-Status-Code' => 200));
As of Symfony 3.3, call
``GetResponseForExceptionEvent::allowCustomResponseCode()`` first and then ``GetResponseForExceptionEvent::allowCustomResponseCode()`` first and then
then set the status code on the response as normal. The kernel will then set the status code on the response as normal. The kernel will now use
now use your status code when sending the response to the client. your status code when sending the response to the client. The
The ``GetResponseForExceptionEvent`` is passed to the error callback as a 4th parameter:: ``GetResponseForExceptionEvent`` is passed to the error callback as a 4th
parameter::
use Symfony\Component\HttpFoundation\Response; use Symfony\Component\HttpFoundation\Response;
use Symfony\Component\HttpFoundation\Request; use Symfony\Component\HttpFoundation\Request;
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment