Open tianxiao1988 opened 1 year ago
Hi! It is not stange, it is standard looking HTTP message, for chunked
encoding. 2ca
indicates how much bytes to read next, and 0
means message is finished. So thats exactly how your server received the data. If you want more human optimised version you can add --prettify-http
flag.
As for linux try adding --input-raw-override-snaplen
argument.
Thanks replay~~
but add --input-raw-override-snaplen still not work, any other suggestion ?
also try to add input-raw-buffer-size 10485760, add --prettify-http, but not work either @buger need your help~~~
I'm using goreplay to capture request and response. My command is: gor --input-raw :8080 --output-stdout --input-raw-track-response. On Mac os, I can capture the request and response, but the response is strange, it's not a valid response, looks like:
2 d78522b57f000001012812a1 1663669556688042000 246000 HTTP/1.1 200 Vary: Origin Vary: Access-Control-Request-Method Vary: Access-Control-Request-Headers Content-Type: application/json Transfer-Encoding: chunked Date: Tue, 20 Sep 2022 10:25:56 GMT Keep-Alive: timeout=60 Connection: keep-alive
2ca {"code":200, "msg":"abcd"} 0
🐵🙈🙉
On Linux, the same api and same gor command, I can't capture response, only request.
I don't know why. gor version is 1.3.3