Mapping rules matching for GET vs POST about apicast HOT 5 CLOSED

Well, I'd say it's a "common" way to do it - like it's assuming form-urlencoded .... arguably it should depend on the content type and use the body or not, depending on that?

from apicast.

arguably it should depend on the content type and use the body or not, depending on that?

Yes, probably this makes sense.

But then for requests like:

curl -XPOST "http://localhost:8080/test?key=hello" -H "Content-Type: application/json" -d '{"another":"parameter"}'

What would be the behavior? Should the request match or not the 2nd mapping rule?

from apicast.

I would say it would, as the URL+query parameters match the rule.

I'd consider the current behavior dubious - we need to understand if customers rely on this and "fixing it" would be a breaking change.

e.g. if content-type is form-url-encoded then match the rule against the URL plus the parameters in the body....otherwise use the url parameters only

from apicast.

I agree. If content-type is form-url-encoded, merge the body with the url params. Otherwise url params only.

from apicast.

Just the authentication parameters got fixed. This still has to be done for mapping rules.

from apicast.