jellyfin/MediaBrowser.Model/Dlna/StreamInfo.cs, branch v12.0-rc4

Fix malformed query string in StreamInfo.ToUrl() causing 500 error via proxies

2026-02-18T20:08:35Z

StreamInfo.ToUrl() generated URLs like `/master.m3u8?&DeviceId=...` (note `?&`) because `?` was appended to the path and all parameters started with `&`. When the first optional parameter (DeviceProfileId) was null, the result was a malformed query string. This is harmless when clients hit Jellyfin directly (ASP.NET Core tolerates `?&`), but when accessed through a reverse proxy that parses and re-serializes the URL (e.g. Home Assistant ingress via aiohttp/yarl), `?&` becomes `?=&` — introducing an empty-key query parameter. ParseStreamOptions then crashes on `param.Key[0]` with IndexOutOfRangeException. Changes: - StreamInfo.ToUrl(): Track query start position and replace the first `&` with `?` after all parameters are appended, producing valid query strings - ParseStreamOptions: Guard against empty query parameter keys - Tests: Remove .Replace("?&", "?") workaround that masked the bug Co-Authored-By: Claude Opus 4.6

Merge pull request #14809 from lostb1t/fix/subtitleencoder

2026-01-26T11:00:14Z

fix: prevent premature disposal of HTTP subtitle streams

Merge pull request #15926 from abitofevrything/feat/accurate_hls_seeking

2026-01-18T11:17:06Z

Refactor HLS transcode seeking

wip

2025-12-21T13:34:27Z

wip

2025-12-21T13:34:27Z

style: fix return statement indentation in StreamInfo.cs

2025-04-24T06:25:12Z

Style: Fix indentation in StreamInfo.cs

2025-04-24T06:17:33Z

refactor(StreamInfo): reorganize subtitle URL logic and conditions

2025-04-23T10:18:38Z

# Conflicts: # MediaBrowser.Model/Dlna/StreamInfo.cs

Improve dynamic HDR metadata handling (#13277)

2025-04-03T00:06:02Z

* Add support for bitstream filter to remove dynamic hdr metadata * Add support for ffprobe's only_first_vframe for HDR10+ detection * Add BitStreamFilterOptionType for metadata removal check * Map HDR10+ metadata to VideoRangeType.cs Current implementation uses a hack that abuses the EL flag to avoid database schema changes. Should add proper field once EFCore migration is merged. * Add more Dolby Vision Range types Out of spec ones are problematic and should be marked as a dedicated invalid type and handled by the server to not crash the player. Profile 7 videos should not be treated as normal HDR10 videos at all and should remove the metadata before serving. * Remove dynamic hdr metadata when necessary * Allow direct playback of HDR10+ videos on HDR10 clients * Only use dovi codec tag when dovi metadata is not removed * Handle DV Profile 7 Videos better * Fix HDR10+ with new bitmask * Indicate the presence of HDR10+ in HLS SUPPLEMENTAL-CODECS * Fix Dovi 8.4 not labeled as HLG in HLS * Fallback to dovi_rpu bsf for av1 when possible * Fix dovi_rpu cli for av1 * Use correct EFCore db column for HDR10+ * Undo outdated migration * Add proper hdr10+ migration * Remove outdated migration * Rebase to new db code * Add migrations for Hdr10PlusPresentFlag * Directly use bsf enum * Add xmldocs for SupportsBitStreamFilterWithOption * Make `VideoRangeType.Unknown` explicitly default on api models. * Unset default for non-api model class * Use tuples for bsf dictionary for now

Fix StreamInfo.ToUrl (#13808)

2025-03-31T03:37:58Z