Hey there,
It looks like possibly a bad request. If we search the raw stack trace for ".cfc" we'll find a few helpful references, more akin to the usual CF "tag context"~
- taffy.core.baseDeserializer.cfc:35
- taffy.core.baseDeserializer.cfc:13
- taffy.core.api.cfc:825
- taffy.core.api.cfc:627
- taffy.core.api.cfc:209
Looking at the first line shows that we're in the baseDeserializer (part of the mechanics of parsing the incoming request) inside a function called throwError, so we're definitely intentionally throwing an error. Let's see if we can figure out why. Since the error is during the request-parsing phase, we know that your resource code hasn't been executed yet -- Taffy (or your serializer) is just unable to parse the incoming request for some reason.
The next line reference is from further up in baseDeserializer, inside the getFromForm function. So we're attempting to process something encoded as if it were a form submission (not necessarily from a form, just using the same formatting). The line in question, 13, is:
<cfset throwError(400, "You've indicated that you're sending form-encoded data but it doesn't appear to be valid. Aborting request.") />
So taffy thinks that the request should be handled like a form (the content-type header specifies this: application/x-www-form-urlencoded), but the body data does not match the expected formatting. When using this content type, the expected body value follows the pattern:
foo=bar&fizz=buzz&taffy=awesome
It's basically a URL query-string formatting, minus the leading question mark. Taffy is checking for the existence of at least one = and not finding it, thus it's throwing this error.
Hopefully that helps you resolve the issue. Without more details about the request (headers, body, verb, etc) I'm afraid I can't pinpoint anything more specific.
If you think this is a bug (e.g. your request doesn't use the application/x-www-form-urlencoded content-type, or the body does contain an =, please file a bug!)
-Adam