You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MAL-LONG-METHOD currently passes only a 400 or a close, but RFC 9112 §3 says "A server that receives a method longer than any that it implements SHOULD respond with a 501 (Not Implemented) status code." The test's own docs page lists 501 as an appropriate response, and the RFC requirement dashboard cites the same SHOULD-501 for this test; only the validator disagrees. The request is valid syntax (a 100 KB token of tchars), so the 400 rule for grammar mismatches (RFC 9112 §2.2) doesn't apply.
This change accepts 501 alongside 400 and close, as #119 did for 413 in MAL-POST-CL-HUGE-NO-BODY, and updates the docs page's Expected line to match. No current verdict changes except for servers answering 501.
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
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.
MAL-LONG-METHODcurrently passes only a 400 or a close, but RFC 9112 §3 says "A server that receives a method longer than any that it implements SHOULD respond with a 501 (Not Implemented) status code." The test's own docs page lists 501 as an appropriate response, and the RFC requirement dashboard cites the same SHOULD-501 for this test; only the validator disagrees. The request is valid syntax (a 100 KBtokenoftchars), so the 400 rule for grammar mismatches (RFC 9112 §2.2) doesn't apply.This change accepts 501 alongside 400 and close, as #119 did for 413 in
MAL-POST-CL-HUGE-NO-BODY, and updates the docs page's Expected line to match. No current verdict changes except for servers answering 501.Edit: Closes #162