Joshua Thijssen
24a287f492
Don't add Accept-Range header on unsafe HTTP requests
2015-01-03 11:53:03 +01:00
Fabien Potencier
73dddac4e0
[HttpFoundation] removed wrong HTTP header
2014-12-25 20:39:31 +01:00
Fabien Potencier
369aebf431
fixed CS
2014-09-22 10:32:35 +02:00
nervo
e1eb788d2f
Use getPathname() instead of string casting to get BinaryFileReponse file path
2014-09-17 13:01:47 +02:00
Julien Pauli
1c5c694196
Fix mocks to support >=5.5.14 and >=5.4.30
2014-06-27 08:53:23 +02:00
Christian Flothmann
2c726b8988
don't disable constructor calls to mockups of classes that extend internal PHP classes
2014-06-20 17:17:50 +02:00
Seb Koelen
9247ef5e27
fix test src/Symfony/Component/HttpFoundation/Tests/BinaryFileResponseTest.php
2014-06-15 10:49:34 +02:00
Simon Schick
57ee5193d0
BinaryFileResponse should also return 416 or 200 on some range-requets
2013-12-16 20:50:58 +01:00
Nicolas Le Goff
4c51ec7866
Fix download over SSL using IE < 8 and binary file response
2013-04-12 15:45:42 +02:00
Jakub Zalas
381bd7e235
[HttpFoundation] Added support for partial ranges in the BinaryFileResponse.
...
Valid ranges include:
* bytes=0-499
* bytes=500-999
* bytes=-500
* bytes=9500-
* bytes=0-0
2013-02-09 16:41:39 +01:00
Jakub Zalas
d9b91458f1
[HttpFoundation] Fixed byte ranges in the BinaryFileResponse.
...
According to rfc2616 (http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.35.1 )
byte positions are inclusive:
The first-byte-pos value in a byte-range-spec gives the byte-offset of
the first byte in a range. The last-byte-pos value gives the byte-offset
of the last byte in the range; that is, the byte positions specified are
inclusive. Byte offsets start at zero.
2013-02-09 16:41:27 +01:00
Fabien Potencier
b27b749025
made usage of Composer autoloader for subtree-split unit tests
2012-11-09 14:10:06 +01:00
Niklas Fiekas
2f7bbbfec1
[HttpFoundation] Added BinaryFileResponse.
2012-08-08 17:25:51 +02:00