27 Commits (abd74fd5a481d67af1414960be7b7b19c9ee7e82)

Author	SHA1	Message	Date
Patrick Barron	abd74fd5a4	Move TranscodingJobDto and TranscodingThrottler to Controller	11 months ago
Shadowghost	f5f890e685	Migrate to file-scoped namespaces	2 years ago
SenorSmartyPants	d5e7e75421	Remove unused httpContext parameter	3 years ago
SenorSmartyPants	3ea54a8009	Remove isHeadRequest from GetStaticFile method signatures	3 years ago
SenorSmartyPants	bd2bec4d4a	Remove special HTTP HEAD processing ... removing this allows HTTP 206 Partial Content responses and lets some clients(popcorn hour namely) play videos from JF.	3 years ago
Bond_009	13fbfe6091	Target net6.0	3 years ago
Szymon Acedański	b1e8a8565f	Update Jellyfin.Api/Helpers/FileStreamResponseHelpers.cs ... Co-authored-by: Claus Vium <cvium@users.noreply.github.com>	4 years ago
Szymon Acedański	136136dea9	Fix incorrect responses for HEAD /audio/<id>/stream ... 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.	4 years ago
BaronGreenback	d819a1d928	Remove Content-Length header from DLNA HEAD request (#5335)	4 years ago
Bond_009	e9f22303a4	Properly forward cancellationTokens	4 years ago
Bond_009	4b1c9dc9ea	Pass cancellation where possible	4 years ago
crobibero	01355e0498	Fix nullability errors in Jellyfin.Api (part 1)	4 years ago
cvium	6ca313abc1	Add ProgressiveFileStream	4 years ago
BaronGreenback	25e965b85c	Update FileStreamResponseHelpers.cs	4 years ago
BaronGreenback	d3e8834e80	Removed memoryStream	4 years ago
David	4836f14aff	Enable HTTP Range Processing	4 years ago
Anthony Lavado	634ee2d1e9	Merge pull request #3861 from crobibero/fixes ... API Fixes	4 years ago
crobibero	be67528958	add disposal docs	4 years ago
crobibero	767c73e5c1	fix usings	4 years ago
crobibero	c5e9cf15f6	Use proper IHttpContextAccessor	4 years ago
crobibero	f543a17d1b	Apply review fixes	4 years ago
crobibero	b8d327889b	Add missing functions	4 years ago
David	ca3dcc3db0	Fix suggestions from review	4 years ago
David	d39f481a5c	Apply suggestions from review	4 years ago
David	2ce97c022e	Move AudioService to Jellyfin.Api	4 years ago
David	07e56850be	Remove caching and content length	4 years ago
David	3514813eb4	Continute work	4 years ago