Clarify request types in cloudfront proxy documentation#447
Open
joyceyan wants to merge 1 commit intoplausible:masterfrom
Open
Clarify request types in cloudfront proxy documentation#447joyceyan wants to merge 1 commit intoplausible:masterfrom
joyceyan wants to merge 1 commit intoplausible:masterfrom
Conversation
I just wanted to clarify what types of requests to `/js/script.js` and `/api/event` would result in successful responses. I spent a lot of time wondering why a GET request to `/api/event` would 404 instead of returning a 202. Sending a POST request via curl seems to be fine, and the API docs seem to indicate there isn't a GET request for `/api/event` so it doesn't seem like it's a problem for that to 404.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I just wanted to clarify what types of requests to
/js/script.jsand/api/eventwould result in successful responses. I spent a lot of time wondering why a GET request to/api/eventwould 404 instead of returning a 202. Sending a POST request via curl seems to be fine, and the API docs seem to indicate there isn't a GET request for/api/eventso it doesn't seem like it's a problem for that to 404.