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

Correct 404 or 401 on APIs instead of 301 #28

Open
pyby opened this issue Jul 23, 2019 · 1 comment
Open

Correct 404 or 401 on APIs instead of 301 #28

pyby opened this issue Jul 23, 2019 · 1 comment
Labels
bug Something isn't working

Comments

@pyby
Copy link
Member

pyby commented Jul 23, 2019

As an API user, I expect to have the correct 4XX response, instead of a redirect.

How to test:
https://[HOST]/api/v2/deeplink/parse_play_url.js -> 404.
https://[HOST]/api/v1/deeplink/report -> 403.

@pyby pyby added bug Something isn't working enhancement New feature or request and removed enhancement New feature or request labels Jul 23, 2019
@pyby
Copy link
Member Author

pyby commented Sep 2, 2019

#36 will fix deeplink API url.

https://[HOST]/api/v[x|/deeplink/parse_play_url.js -> 404. with x > 2.
v1 and v2 now available.

@pyby pyby changed the title 301 instead of correct 404 or 401 on APIs Correct 404 or 401 on APIs instead of 301 Aug 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant