aboutsummaryrefslogtreecommitdiff
path: root/Jellyfin.Api/Helpers/FileStreamResponseHelpers.cs
AgeCommit message (Collapse)Author
2025-04-29Enhanced HTTP Range request support for. strm filesususu98
Forward the Range, Accept-Ranges, and Content- Range headers, improve User-Agent handling, and adjust the default Content-Type.
2024-07-20Don't buffer content in GetStaticRemoteStreamResultBond_009
2024-01-03AsyncKeyedLock migrationMark Cilia Vincenti
2023-12-21Add ITranscodeManager servicePatrick Barron
2023-12-21Rename and clean up TranscodingJobPatrick Barron
2023-12-21Move TranscodingJobDto and TranscodingThrottler to ControllerPatrick Barron
2023-02-02Migrate to file-scoped namespacesShadowghost
2022-01-08Remove unused httpContext parameterSenorSmartyPants
2022-01-07Remove isHeadRequest from GetStaticFile method signaturesSenorSmartyPants
2022-01-07Remove special HTTP HEAD processingSenorSmartyPants
removing this allows HTTP 206 Partial Content responses and lets some clients(popcorn hour namely) play videos from JF.
2021-09-24Target net6.0Bond_009
2021-03-24Update Jellyfin.Api/Helpers/FileStreamResponseHelpers.csSzymon Acedański
Co-authored-by: Claus Vium <cvium@users.noreply.github.com>
2021-03-24Fix incorrect responses for HEAD /audio/<id>/streamSzymon Acedański
Without this fix my Samsung Soundbar (HW-Q80R) fails to play using DLNA and returns "Error: Resource not found (716)" instead. I had a look on tcpdump network logs between Jellyfin and the soundbar and noticed that the device performs a HEAD request for the media before responding to the DLNA UPNP control request from Jellyfin (or BubbleUPNP Android App). Jellyfin retuns 204 No Content response, which is unusual. Common web servers generally return 200 OK if the GET would return content, and this is not-very-clearly suggested [in HTTP spec](https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.1) The other patch is to ensure, that invalid Content-Length: 0 is not returned with the HEAD response in the streaming case. I think in both cases we still don't return the same headers with HEAD as with GET (e.g. Content-Length or Accept-Ranges), but at least we don't return anything misleading.
2021-03-03Remove Content-Length header from DLNA HEAD request (#5335)BaronGreenback
2021-02-15Properly forward cancellationTokensBond_009
2020-11-17Pass cancellation where possibleBond_009
2020-11-13Fix nullability errors in Jellyfin.Api (part 1)crobibero
2020-09-25Add ProgressiveFileStreamcvium
2020-09-05Update FileStreamResponseHelpers.csBaronGreenback
2020-09-05Removed memoryStreamBaronGreenback
2020-09-05Enable HTTP Range ProcessingDavid
2020-08-19Merge pull request #3861 from crobibero/fixesAnthony Lavado
API Fixes
2020-08-17add disposal docscrobibero
2020-08-17fix usingscrobibero
2020-08-10Use proper IHttpContextAccessorcrobibero
2020-07-30Apply review fixescrobibero
2020-07-27Add missing functionscrobibero
2020-07-24Fix suggestions from reviewDavid
2020-07-23Apply suggestions from reviewDavid
2020-07-22Move AudioService to Jellyfin.ApiDavid
2020-07-22Remove caching and content lengthDavid
2020-07-19Continute workDavid