codeconsole commented on PR #16149: URL: https://github.com/apache/grails-core/pull/16149#issuecomment-5499155236
The end-to-end test now exists: 9763091 adds `RequestPathSpec` in app1, driving a real server through the servlet filter chain. One round trip asserts the whole chain agrees: a multipart form POST naming PUT is resolved by the dispatcher after multipart parsing, the mapping picks the PUT route, `allowedMethods` admits it by the effective method, the multipart text field and the uploaded file both reach `params`, a command object binds from them, the response renders — and `request.method` still reports the POST it arrived as. Five more cases pin the surrounding behaviour: a bare POST to the member URL reaches `update` (#9926, and only routable while the filter is off); a form POST naming DELETE reaches `delete`; one naming PATCH reaches `patch` rather than `update`, which is what the suppressed `_method` used to break; a POST naming GET stays a POST; a real DELETE routes as itself. Spring Security is the one dimension on your list this cannot cover — app1 does not have it on the classpath. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
