You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
curl -v localhost:9090/transform/chamil/go/elle/gamage
* Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to localhost (127.0.0.1) port 9090 (#0)
> GET /transform/chamil/go/elle/gamage HTTP/1.1
> Host: localhost:9090
> User-Agent: curl/7.64.1
> Accept: */*
>
< HTTP/1.1 404 Not Found
< content-type: text/plain
< content-length: 85
< server: ballerina
< date: Sat, 21 Mar 2020 18:19:08 +0530
<
* Connection #0 to host localhost left intact
no matching resource found for path : /transform/chamil/go/elle/gamage
Request 2
curl -v localhost:9090/transform/chamil/go/elle/gamage
* Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to localhost (127.0.0.1) port 9090 (#0)
> GET /transform/chamil/go/elle/gamage HTTP/1.1
> Host: localhost:9090
> User-Agent: curl/7.64.1
> Accept: */*
>
< HTTP/1.1 404 Not Found
< content-type: text/plain
< content-length: 85
< server: ballerina
< date: Sat, 21 Mar 2020 18:19:04 +0530
<
* Connection #0 to host localhost left intact
no matching resource found for path : /transform/chamil/go/elle/gamage , method : GET* Closing connection 0
Observation
If path changes as follows, it works fine
resource 1 - path:"/{aaa}/go/{bbb}"
resource 2 - path:"{aaa}/go/{bbb}/{ccc}"
HttpResourceArguments collects all path param values against the identifier. If the same identifier occurs again, then the value is getting replaced.
This condition skips getting the same param getting replaced, but that condition is incorrect.
Affected Versions:
v1.2.0
The text was updated successfully, but these errors were encountered:
chamil321
changed the title
Dispatching fails when same path param identifiers exist in a different order
[HTTP][Dispatching] Dispatching fails when same path param identifiers exist in a different order
Mar 23, 2020
chamil321
changed the title
[HTTP][Dispatching] Dispatching fails when same path param identifiers exist in a different order
[HTTP] Dispatching fails when same path param identifiers exist in a different order
Mar 23, 2020
Description:
$Subject
Steps to reproduce:
Request 1
Request 2
Observation
Affected Versions:
v1.2.0
The text was updated successfully, but these errors were encountered: