Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot send request when too many songs are selected #2483

Open
Ainto opened this issue Oct 30, 2020 · 12 comments
Open

Cannot send request when too many songs are selected #2483

Ainto opened this issue Oct 30, 2020 · 12 comments
Labels
bug Something isn't working confirmed The issue has been verified

Comments

@Ainto
Copy link

Ainto commented Oct 30, 2020

Describe the bug

The request cannot be sent when too many songs are selected in the playlist.
For example: save all songs in the current play queue to a new playlist.

System (please complete the following information):

  • OS: QNAP
  • Virtualization: Docker
  • Clients: Browser
  • Browser: Microsoft Edge 88.0.680.1
  • Jellyfin Version: 10.6.3
  • Base URL: none

To Reproduce

  1. Add some music to the playback queue
  2. Click "save icon" (add to playlist) and click "add"

Expected behavior

In the browser devtools network

Request URL: http://192.168.1.xxx:8096/Playlists?Name=XXX&Ids=[Very long]
Request Method: POST
Status Code: 414 URI Too Long

@BaronGreenback
Copy link
Contributor

This is a design issue, with the API using url parameter passing, which limits it to 2000 characters.

@TheNamelessWonderer
Copy link

Is there a solution to this? I have the same issue but with a song that won't play because of this issue.

@crobibero
Copy link
Member

The fix would be to update web to post the data instead of using query parameters

@TheNamelessWonderer
Copy link

TheNamelessWonderer commented Mar 6, 2021

The issue is I have an album with 270 tracks. If I choose the first one it adds all of them to a queue and thus causes URI too long and won't play the first track at all. I am running 10.7-RC4.

@crobibero
Copy link
Member

I understand, the API accepts the request as a POST with the contents as the body or as query parameters. I originally migrated the API to only allow body but web still uses query parameters. This is not a server issue

@TheNamelessWonderer
Copy link

TheNamelessWonderer commented Mar 6, 2021

Should the issue be transferred to Jellyfin-Web if it isn't a server issue?

@Bond-009 Bond-009 transferred this issue from jellyfin/jellyfin Mar 6, 2021
@Zagitta
Copy link

Zagitta commented Mar 26, 2021

This also seems to be an issue when using syncplay and attempting to play an episode as
GET https://jelly.my.domain/Users/[user uuid]/Items?Ids=[very long] results in a http 414 error

@stale
Copy link

stale bot commented Jun 26, 2021

Issues go stale after 90d of inactivity. Mark the issue as fresh by adding a comment or commit. Stale issues close after an additional 14d of inactivity. If this issue is safe to close now please do so. If you have any questions you can reach us on Matrix or Social Media.

@stale stale bot added the stale No activity for an extended length of time label Jun 26, 2021
@thornbill thornbill added confirmed The issue has been verified bug Something isn't working and removed stale No activity for an extended length of time labels Jun 26, 2021
@oddstr13
Copy link
Member

oddstr13 commented Apr 7, 2022

This issue is also present when attempting to play a series episode from a show with many episodes per season in a SyncPlay group.

@EliseRemise
Copy link

Thanks Bond-009 this is it. I see it has been here fore a while. Haven't tried Emby but these problems are on there forum too. Altough they claim to have increased the number off tracks.

@EliseRemise
Copy link

Just saw the fix is waiting on approval: #4221

@dann-merlin
Copy link
Contributor

Please note that the PR #4221 will fix the usage of the /Users/<hex userid>/Items?... endpoint, but not the original issue, as that is another endpoint that would require another fix itself. As I'm not affected by the playlist issue, I did not bother to fix this and am also not planning to (I don't have a lot of fun with typescript, sorry ^^). I'm sure however that the fix should be straight forward for anyone doing it themselves as it would pretty much be the same as my PR just for another endpoint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working confirmed The issue has been verified
Projects
No open projects
Release 10.8.0
  
Active Bugs
Development

No branches or pull requests

9 participants