When sending a POST request with JSON Request body type, RESTED appears to strip double slashes from the JSON body. This does not happen when sending the Request as a Custom body type. This was noticed when sending base64 encoded images.
Note: this appears to be related to issue #119 but affects the body instead of the headers.
send Request
Response from postman-echo:
{ "args": {}, "data": { "mydata": "//This is a /test" } ...,
Interestingly, the first double slash is preserved but subsequent ones are converted to single slash. The same happens with 3 slashes. Didn't test with more than 3
Modify the same request but with body type of Custom:
{"mydata":"//This is a //test"}
Response from postman-echo:
{ "args": {}, "data": { "mydata": "//This is a //test" }, ...
When sending a POST request with JSON Request body type, RESTED appears to strip double slashes from the JSON body. This does not happen when sending the Request as a Custom body type. This was noticed when sending base64 encoded images.
Note: this appears to be related to issue #119 but affects the body instead of the headers.
Steps to reproduce:
application/jsonmydata-->//This is a //test{ "args": {}, "data": { "mydata": "//This is a /test" } ...,Interestingly, the first double slash is preserved but subsequent ones are converted to single slash. The same happens with 3 slashes. Didn't test with more than 3
Modify the same request but with body type of Custom:
{"mydata":"//This is a //test"}Response from postman-echo:{ "args": {}, "data": { "mydata": "//This is a //test" }, ...In this case the correct data is sent.