| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2025-04-29 | Enhanced HTTP Range request support for. strm file | sususu98 | |
| Forward the Range, Accept-Ranges, and Content- Range headers, improve User-Agent handling, and adjust the default Content-Type. | |||
| 2024-07-20 | Don't buffer content in GetStaticRemoteStreamResult | Bond_009 | |
| 2024-01-03 | AsyncKeyedLock migration | Mark Cilia Vincenti | |
| 2023-12-21 | Add ITranscodeManager service | Patrick Barron | |
| 2023-12-21 | Rename and clean up TranscodingJob | Patrick Barron | |
| 2023-12-21 | Move TranscodingJobDto and TranscodingThrottler to Controller | Patrick Barron | |
| 2023-02-02 | Migrate to file-scoped namespaces | Shadowghost | |
| 2022-01-08 | Remove unused httpContext parameter | SenorSmartyPants | |
| 2022-01-07 | Remove isHeadRequest from GetStaticFile method signatures | SenorSmartyPants | |
| 2022-01-07 | Remove special HTTP HEAD processing | SenorSmartyPants | |
| removing this allows HTTP 206 Partial Content responses and lets some clients(popcorn hour namely) play videos from JF. | |||
| 2021-09-24 | Target net6.0 | Bond_009 | |
| 2021-03-24 | Update Jellyfin.Api/Helpers/FileStreamResponseHelpers.cs | Szymon Acedański | |
| Co-authored-by: Claus Vium <cvium@users.noreply.github.com> | |||
| 2021-03-24 | Fix incorrect responses for HEAD /audio/<id>/stream | Szymon 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-03 | Remove Content-Length header from DLNA HEAD request (#5335) | BaronGreenback | |
| 2021-02-15 | Properly forward cancellationTokens | Bond_009 | |
| 2020-11-17 | Pass cancellation where possible | Bond_009 | |
| 2020-11-13 | Fix nullability errors in Jellyfin.Api (part 1) | crobibero | |
| 2020-09-25 | Add ProgressiveFileStream | cvium | |
| 2020-09-05 | Update FileStreamResponseHelpers.cs | BaronGreenback | |
| 2020-09-05 | Removed memoryStream | BaronGreenback | |
| 2020-09-05 | Enable HTTP Range Processing | David | |
| 2020-08-19 | Merge pull request #3861 from crobibero/fixes | Anthony Lavado | |
| API Fixes | |||
| 2020-08-17 | add disposal docs | crobibero | |
| 2020-08-17 | fix usings | crobibero | |
| 2020-08-10 | Use proper IHttpContextAccessor | crobibero | |
| 2020-07-30 | Apply review fixes | crobibero | |
| 2020-07-27 | Add missing functions | crobibero | |
| 2020-07-24 | Fix suggestions from review | David | |
| 2020-07-23 | Apply suggestions from review | David | |
| 2020-07-22 | Move AudioService to Jellyfin.Api | David | |
| 2020-07-22 | Remove caching and content length | David | |
| 2020-07-19 | Continute work | David | |
