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

Ampache returns error 405 instead of 404 after deleting playlist #3844

Open
memen45 opened this issue Feb 28, 2024 · 3 comments
Open

Ampache returns error 405 instead of 404 after deleting playlist #3844

memen45 opened this issue Feb 28, 2024 · 3 comments

Comments

@memen45
Copy link

memen45 commented Feb 28, 2024

Description

Describe the bug

To reproduce

Steps to reproduce the behavior:

  • Create a playlist
  • request playlist through the api using the id (working fine)
  • delete the playlist from the server
  • request playlist through the api using the id
  • receive Ampache 405 error

Expected behavior

  • receive Ampache 404 error

Environment

  • Ampache version: 6.2.1
  • Web server + version: nginx
  • Server operating system: docker container
  • Client operating system: Garmin OS

Client type

SubMusic v0.2.12
Requests API version: 440000

Logs

@haelduksf

@haelduksf
Copy link

All I'm seeing in the Ampache logs with debug_level=5 is
2024-04-10T01:35:59+00:00 [admin] (Ampache\Module\System\Session) -> d[...]e has been extended to Wed, 10 Apr 2024 02:35:59 +0000 extension length 3600 2024-04-10T01:35:59+00:00 [ampache] (Ampache\Module\System\Dba) -> Database connection... 2024-04-10T01:35:59+00:00 [ampache] (Ampache\Module\Api\Authentication\Gatekeeper) -> API session [d[...]e] 2024-04-10T01:35:59+00:00 [admin] (Ampache\Module\Api\ApiHandler) -> API function [Ampache\Module\Api\Method\Api4\Playlist4Method] 2024-04-10T01:35:59+00:00 [admin] (Ampache\Module\Api\ApiHandler) -> Typed property Ampache\Repository\Model\playlist_object::$type must not be accessed before initialization

Is that helpful or do I need to figure out how to get the text of the 405?

@lachlan-00
Copy link
Member

the api is catching the error and returning 405.

i shuld actually include an option to bypass this error catching for better debug

@lachlan-00
Copy link
Member

set with acf09d7, i'll look at options of disabling error catching too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants