Does anyone know if ColdFusion 2023 handles the PA...
# adobe
d
Does anyone know if ColdFusion 2023 handles the PATCH and MERGE verbs correctly? We're using the BonCode connector and we're seeing form data being sent with PATCH going missing and perhaps coming through as binary. Some screenshots on my last comment here to illustrate the weirdness: https://github.com/Bilal-S/iis2tomcat/issues/40 Would be good to know if anyone using ACF 2023 is using PATCH/MERGE verbs successfully.
w
if memory serves it's a limitation of the boncode connector. we found there was no way to force it to honor PATCH so we ended up using PROPPATCH which was lame but easy since we were consuming our own api
sorry, just checked and i had added a note that it's a limitation in the AJP protocol, not boncode per se
d
@websolete the latest boncode connector handles that issue, it passes it through. You can see the PATCH verb coming through fine in CF. It's like ACF only passes form data through on a POST, doesn't know what to do with a PATCH.
So to confirm, the VERB http method works fine, just the form-data passed in isn't coming through. Empty FORM scope.
r
prob CF expects POST to be mapped to FORM, so for PATCH you will have to take raw request data and parse it - I remember we avoided URL/FORM scopes altogether and used raw request data when created REST API
d
@Mark Takata (Adobe) could one of your team shed some light on this? PATCH is pretty common in the REST API world. Could a future CF update allow PATCH to receive form data?