-
Notifications
You must be signed in to change notification settings - Fork 41
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
POST api.clearlydefined.io/definitions returns unexpected data when using http protocol instead of https #621
Comments
Hello, and thank you for this! Sorry to ask but what is the data you were expecting, or rather mainly how does the actual response differ from it? |
@ignacionr The responses are different for |
I see. It’s interesting. CloudFlare is only doing http, I assume? Not working as https termination right? |
That is exactly what is happening; the thing is POST doesn't really make proper redirects. Further explanation of what is happening (and why we endup getting the GET resource) can be found here. |
Closing this issue as the direct/practical solution is for API users to understand and cope with POST redirects (which are a special non-trivial case, around the defined HTTP behavior).
|
For example:
Post http://api.clearlydefined.io/definitions
Body: ["npm/npmjs/-/redie/0.1.0"]
Response Json:
The text was updated successfully, but these errors were encountered: