Added minor clarification

[ThomasLandauer]

It was not clear if the following code applies to BinaryFileResponse only or to all file responses.

Since the following two paragraphs ("It is possible to delete ..." and "If you just created...") also apply to BinaryFileResponse only, it would be even better to have a separate heading for BinaryFileResponse, but I don't know how to create another sub-heading at this level.

[wouterj]

👍 (it's not 100% true as headers can be set on each response type, but we document that should be easy to discover)

[ThomasLandauer]

@wouterj: There's a typo in your comment, so I'm not sure about what you're saying ;-)

Anyway - my point:
If I do the following:

$response = new Response($dompdf->output());      
$response->setContentDisposition(
    ResponseHeaderBag::DISPOSITION_ATTACHMENT,
    'filename.txt'
);

I get: Fatal error: Call to undefined method Symfony\Component\HttpFoundation\Response::setContentDisposition()

...since setContentDisposition() is a method of BinaryFileResponse http://api.symfony.com/2.3/Symfony/Component/HttpFoundation/BinaryFileResponse.html but not of the "regular" Response object http://api.symfony.com/2.3/Symfony/Component/HttpFoundation/Response.html

In the original sentence in the docs ("You can still set..."), it's not clear if "still" means after $response = new BinaryFileResponse($file); or after the (implied) $response = new Response(...) of the use Symfony\Component\HttpFoundation\ResponseHeaderBag;... code sample.

[weaverryan]

I like it - nice clarification. And I agree with Wouter's comments. Good PR - thanks Thomas!