starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-07-16 05:43:54 +03:00
Code Issues 822 Packages Projects Releases 17 Wiki Activity

[PR #3319] [MERGED] Use Http status code 204 instead of 200 #9447

New Issue
Closed
opened 2026-02-07 06:02:18 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-07 06:02:18 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/jellyfin/jellyfin/pull/3319
Author: @daullmer
Created: 6/12/2020
Status: ✅ Merged
Merged: 6/15/2020
Merged by: @dkanada

Base: api-migration ← Head: api-204

📝 Commits (2)

  • 043d76b Use Http status code 204 instead of 200
  • 9bedd9a Merge remote-tracking branch 'upstream/api-migration' into api-204

📊 Changes

5 files changed (+53 additions, -52 deletions)

View changed files

📝 Jellyfin.Api/Controllers/ConfigurationController.cs (+9 -9)
📝 Jellyfin.Api/Controllers/DevicesController.cs (+8 -8)
📝 Jellyfin.Api/Controllers/NotificationsController.cs (+12 -12)
📝 Jellyfin.Api/Controllers/PackageController.cs (+8 -7)
📝 Jellyfin.Api/Controllers/StartupController.cs (+16 -16)

📄 Description

Changes
Switch to use Http status code 204 instead of 200 when returning no result in Jellyfin,Api.
The old Api endpoint checks if the response is empty and returns 204 instead of 200.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/jellyfin/jellyfin/pull/3319 **Author:** [@daullmer](https://github.com/daullmer) **Created:** 6/12/2020 **Status:** ✅ Merged **Merged:** 6/15/2020 **Merged by:** [@dkanada](https://github.com/dkanada) **Base:** `api-migration` ← **Head:** `api-204` --- ### 📝 Commits (2) - [`043d76b`](https://github.com/jellyfin/jellyfin/commit/043d76bd6e9e4a2e1093ae0e5ba025de1438b528) Use Http status code 204 instead of 200 - [`9bedd9a`](https://github.com/jellyfin/jellyfin/commit/9bedd9ac3ca5b5854acd6891e746bf2e7225ff21) Merge remote-tracking branch 'upstream/api-migration' into api-204 ### 📊 Changes **5 files changed** (+53 additions, -52 deletions) <details> <summary>View changed files</summary> 📝 `Jellyfin.Api/Controllers/ConfigurationController.cs` (+9 -9) 📝 `Jellyfin.Api/Controllers/DevicesController.cs` (+8 -8) 📝 `Jellyfin.Api/Controllers/NotificationsController.cs` (+12 -12) 📝 `Jellyfin.Api/Controllers/PackageController.cs` (+8 -7) 📝 `Jellyfin.Api/Controllers/StartupController.cs` (+16 -16) </details> ### 📄 Description **Changes** Switch to use Http status code 204 instead of 200 when returning no result in Jellyfin,Api. The old Api endpoint checks if the response is empty and returns 204 instead of 200. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-07 06:02:18 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#9447
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?