-
Notifications
You must be signed in to change notification settings - Fork 337
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
"Path not supported by Algolia REST API" #471
Comments
kyleboe
added a commit
to kyleboe/hackney
that referenced
this issue
Jul 19, 2023
It is actually a bug in the url spec implementation by hackney. I fixed it here: benoitc/hackney#720 |
benoitc
pushed a commit
to benoitc/hackney
that referenced
this issue
Oct 10, 2023
The fix was merged into hackney |
kyleboe
added a commit
to kyleboe/httpoison
that referenced
this issue
Oct 11, 2023
edgurgel
pushed a commit
that referenced
this issue
Nov 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm encountering the same problem as in #116 issue from 2016.
Possibly the asterisk in the url is causing it. It could be issue with Hackney.
I tried looking at the code but I'm not competent enough to troubleshoot it.
The issue:
$ curl 'https://m19dxw5x0q-dsn.algolia.net/1/indexes/*/queries' --data-raw ''
returns "400, no content in POST request", as expectedHTTPoison.post! "https://m19dxw5x0q-3.algolianet.com/1/indexes/*/queries", ""
returns "404, path not supported by Algolia REST API", despite it being a valid pathProper instructions to reproduce:
https://fontawesome.com/search?q=poison
(or try other websites using Algolia)The text was updated successfully, but these errors were encountered: