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
When an API request contains an extra / in the path (tested with .../pipeline//api/...) the cleanup redirect looses the request method (tested with POST -> GET). which causes unexpected behavior and silent "failure" in case of modifying operations (tested with node pool create).
Observe the Pipeline logs to contain something similar to the description snippet above.
Expected behavior
The Pipeline should keep the request method when redirecting due to extra slashes.
Screenshots
Additional context
The new router replies to paths with // with a http redirect, which results in a GET request instead of POSTs in the go client (at the very least regarding trailing slashes).
The text was updated successfully, but these errors were encountered:
Describe the bug
When an API request contains an extra
/
in the path (tested with .../pipeline//api/...) the cleanup redirect looses the request method (tested withPOST
->GET
). which causes unexpected behavior and silent "failure" in case of modifying operations (tested with node pool create).Steps to reproduce the issue:
/
. (replace the token placeholder)Expected behavior
The Pipeline should keep the request method when redirecting due to extra slashes.
Screenshots
Additional context
The new router replies to paths with
//
with a http redirect, which results in a GET request instead of POSTs in the go client (at the very least regarding trailing slashes).The text was updated successfully, but these errors were encountered: