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
#1. I am using golang Resty to execute APIs against vault
#2. My mount post api works the first time , namely 204 No Content. Verified also on vault that it exists.
Btw Resty complains with the
*** Error: Unable to format response body - "unexpected end of JSON input" *** but that's another issue
#3. I do not change anything and submit the same request, in which I am expecting
"errors": [
"path is already in use at winter/rush21124/"
]
#4. Unfortunately I do not and get the same result , namely 204 No Content , i.e. - same as #1
#5. Seems if I rebuild my go and execute the same unit test ... then i get the expected outcome
"errors": [
"path is already in use at winter/rush21124/"
]
Is there some kind of caching of against rest clients in which the same response is returned regardless ?
The text was updated successfully, but these errors were encountered:
Hi @lanpar ! Thanks for submitting the issue, I've added some labels as I found appropriate. However, I think this issue could use a little bit more detail probably, could you maybe share some code snippets that you're running, so we can run the same when we try to repro this ?
#1. I am using golang Resty to execute APIs against vault
#2. My mount post api works the first time , namely 204 No Content. Verified also on vault that it exists.
Btw Resty complains with the
*** Error: Unable to format response body - "unexpected end of JSON input" *** but that's another issue
#3. I do not change anything and submit the same request, in which I am expecting
"errors": [
"path is already in use at winter/rush21124/"
]
#4. Unfortunately I do not and get the same result , namely 204 No Content , i.e. - same as #1
#5. Seems if I rebuild my go and execute the same unit test ... then i get the expected outcome
"errors": [
"path is already in use at winter/rush21124/"
]
Is there some kind of caching of against rest clients in which the same response is returned regardless ?
The text was updated successfully, but these errors were encountered: