Incident Dossier
HTTP method casing mishandled for non-standard verbs
A Request constructor accepts a method option. The library normalizes the six standard HTTP methods (DELETE, GET, HEAD, OPTIONS, POST, PUT) to uppercase regardless of input casing, while preserving every other method string exactly as supplied. Currently, the casing rule applies too broadly, altering method names that should pass through untouched.
Initial failing signalNon-standard method casing alteredExpected behavior: Standard methods (DELETE, GET, HEAD, OPTIONS, POST, PUT) normalize to uppercase regardless of input casing; any other method string is preserved exactly as supplied. · actual behavior: Non-standard method strings such as 'patch' and 'chicken' are being transformed (e.g., uppercased) instead of preserved exactly as written.