nextcloud/build/integration/data
Lukas Reschke 8a00638425
Don't set Content-Disposition header if one already exists
If a Content-Disposition header is already set by another plugin we don't need to set another one as this breaks clients.

Fixes https://github.com/nextcloud/server/issues/1992

Signed-off-by: Lukas Reschke <lukas@statuscode.ch>
2016-12-14 17:35:27 +01:00
..
bjoern.vcf Don't set Content-Disposition header if one already exists 2016-12-14 17:35:27 +01:00
textfile.txt add behat tests for 0 quota upload failure 2015-12-01 14:51:32 +01:00