Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chunked responses and secretResponses #83

Open
ciricc opened this issue Dec 11, 2024 · 1 comment
Open

Chunked responses and secretResponses #83

ciricc opened this issue Dec 11, 2024 · 1 comment

Comments

@ciricc
Copy link

ciricc commented Dec 11, 2024

We have the Transfer-Encoding header which value my be chunked. When it is, the response body devided by the chunks:

<chunk_size>
<chunk_content>
\r\n
<chunk_size>
<chunk_content>
\r\n....

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

@themighty1
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants