Method Not Allowed - redirect following bug#224
Open
VitjanZ wants to merge 1 commit into
Open
Conversation
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.
Addressing these Sentry errors:
https://codeplain.sentry.io/issues/7407243122/?project=4510794036674560&query=is%3Aunresolved&referrer=issue-stream
https://codeplain.sentry.io/issues/7229526782/events/recommended/?project=4510794036674560&query=user.ip%3A%2262.4.40.218%22&referrer=issue-stream
We are seeing rare server-side errors at some API calls:
405 Method Not Allowed: The method is not allowed for the requested URL.The 405 for a POST-only call generally means it was redirected and downgraded to a GET request.
The client always sends POST, so a 405 on a POST-only route means the request reached the router as a non-POST which isn't allowed causing the crash. The redirect happens cause of App Engine not directly our server code.
It happens very rarely and currently most often on create_conformance_test_memory because that endpoint carries a large request body (two full test outputs) which may be why it mostly happens here but this payload is still relatively small. I can look into reducing this anyway.
The fix: