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

/archive and /unarchive API routes return 404 #77

Closed
bachya opened this issue Feb 18, 2021 · 1 comment · Fixed by #79
Closed

/archive and /unarchive API routes return 404 #77

bachya opened this issue Feb 18, 2021 · 1 comment · Fixed by #79

Comments

@bachya
Copy link
Contributor

bachya commented Feb 18, 2021

Version: 1.3.1
Architecture: Docker

I'm hosting linkding behind Traefik. I've confirmed that all API endpoints work with my host/token. The exceptions are POST /api/bookmarks/<id>/archive/ and POST /api/bookmarks/<id>/unarchive/, both of which return 404 responses when I query them:

Archive

Request:

POST /api/bookmarks/1/archive/ HTTP/1.1
Authorization: Token REDACTED
Host: REDACTED
Connection: close
User-Agent: Paw/3.2.2 (Macintosh; OS X/11.2.1) GCDHTTPRequest
Content-Length: 0

Response:

HTTP/1.1 404 Not Found
Content-Length: 77
Content-Type: text/html
X-Frame-Options: SAMEORIGIN
Date: Thu, 18 Feb 2021 01:06:19 GMT
Connection: close

<h1>Not Found</h1><p>The requested resource was not found on this server.</p>

Unarchive

Request:

POST /api/bookmarks/1/unarchive/ HTTP/1.1
Authorization: Token REDACTED
Host: REDACTED
Connection: close
User-Agent: Paw/3.2.2 (Macintosh; OS X/11.2.1) GCDHTTPRequest
Content-Length: 0

Response:

HTTP/1.1 404 Not Found
Content-Length: 77
Content-Type: text/html
X-Frame-Options: SAMEORIGIN
Date: Thu, 18 Feb 2021 01:06:19 GMT
Connection: close

<h1>Not Found</h1><p>The requested resource was not found on this server.</p>
@bachya bachya changed the title /archive and /unarchive API routes don't work /archive and /unarchive API routes return 404 Feb 18, 2021
sissbruecker pushed a commit that referenced this issue Feb 18, 2021
sissbruecker pushed a commit that referenced this issue Feb 18, 2021
@sissbruecker
Copy link
Owner

This was due to wrong parameter names, it should be fixed now.

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

Successfully merging a pull request may close this issue.

2 participants