Schema validation not working as expected when "/" available at end of the URL

[LayaniMal]

Description

Schema validation is not working as expected when a trailing slash ("/") is added at the end of the URL.

Steps to Reproduce

• Create a sample API with the SampleSwagger.yaml[1] providing a mock endpoint.
• Enable the schema validation.
• Create an Application, subscribe to the API, and invoke the API with an invalid schema.

Scenario 01

Request

curl --location 'https://localhost:8243/sample/1.0/api/v1/testingEnpoint' \
--header 'accept: */*' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer eyJ4NXQiOiJNell4TW1Ga09HW...' \
--data '{"test":1}'

Response

<am:fault xmlns:am="http://wso2.org/apimanager">
    <am:code>400</am:code>
    <am:message>Bad Request</am:message>
    <am:description>Schema validation failed in the Request: #: expected type: String, found: JSONObject, </am:description>
</am:fault>

Scenario 02

• Add the "/" end of the URL and try out the same request.

Request

curl --location 'https://localhost:8243/sample/1.0/api/v1/testingEnpoint/' \
--header 'accept: */*' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer eyJ4NXQiOiJNell4TW1Ga09HW...' \
--data '{"test":1}'

Response

• Observe the 200 responses as below.

{
    "hello": "world"
}

[1] SampleSwagger.yaml.txt

Affected Component

APIM

Version

3.2.0

Environment Details (with versions)

No response

Relevant Log Output

No response

Related Issues

No response

Suggested Labels

APIM-3.2.0