Nodal 0.7: '501 Not Implemented' on DELETE /access_tokens
See original GitHub issueHi,
I’ve follow your screencast part 3 using nodaljs 0.7.x but stuck on implementing logout.
I got ‘501 Not Implemented’ while doing ‘DELETE /access_tokens’. It’s weird because I already have delete()
method on Access Token Controller. I can doing GET or POST /access_tokens without problem.
Issue Analytics
- State:
- Created 8 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
How to Fix the HTTP 501 Not Implemented Error on Your Site
The HTTP 501 Not Implemented status code indicates that the server does not support the functionality required to fulfill the request.
Read more >octokit/auth-app.js: GitHub App authentication for JavaScript
@octokit/auth-app implements authentication for GitHub Apps using JSON Web Token, installation access tokens, and OAuth user-to-server access tokens.
Read more >Error 501 Not Implemented: how to fix it and main causes
Error 501 HTTP Not Implemented occurs when a site tries to use a method unavailable on the server. In this post we cover...
Read more >Agents - Configuration File Reference | Consul
Use agent configuration files to assign attributes to agents and configure multiple agents at once. Learn about agent configuration file parameters and ...
Read more >Generated Model gives 501 when trying to use the delete on ...
I created a model using the command: slc loopback:model. I did not change anything else, so the model.js is default and the model.json...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@pewh, try changing
destroy()
todel()
and LMK if you have the same issue.The problem is the
destroy
endpoint is only triggered provided an id.It’s work, dude. Thanks! 🍻