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 we have the chunked JSON, it may not find the substring in the response, because the chunk size devided the one of secretResponse. So, the secretResponse will no be hidden:
ff
{"hello": tr
\r\n
16
ue}
0
secretResponses = ["true"]
Will not hide the true, because we have only tr\r\n16ue.
Maybe the Accept-Encoding: identity by default in the all requests will do the trick. But i am not sure bout that
The text was updated successfully, but these errors were encountered:
From my observations, Accept-Encoding: identity will disable the compression but not chunking. I recall that using HTTP 1.0 may disable chunking but ymmv.
We have the
Transfer-Encoding
header which value my bechunked
. When it is, the response body devided by the chunks:When we have the chunked JSON, it may not find the substring in the response, because the chunk size devided the one of secretResponse. So, the secretResponse will no be hidden:
secretResponses =
["true"]
Will not hide the
true
, because we have onlytr\r\n16ue
.Maybe the
Accept-Encoding: identity
by default in the all requests will do the trick. But i am not sure bout thatThe text was updated successfully, but these errors were encountered: