From 45ee54769d28596944f440ade3d4feca92a24699 Mon Sep 17 00:00:00 2001 From: Thomas Gratier Date: Tue, 19 Mar 2024 13:42:49 +0100 Subject: [PATCH] Update Saving-and-Replaying-from-file.md Addition due to #1234 feedbacks. Description for latency borrowed from https://github.com/buger/goreplay/blob/master/middleware/README.md?plain=1#L39C13-L40 --- docs/Saving-and-Replaying-from-file.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/Saving-and-Replaying-from-file.md b/docs/Saving-and-Replaying-from-file.md index 568c7d5a..95b17ecc 100644 --- a/docs/Saving-and-Replaying-from-file.md +++ b/docs/Saving-and-Replaying-from-file.md @@ -67,15 +67,16 @@ To read or write GZIP compressed files ensure that file extension ends with ".gz Gor has memory buffer when it writes to file, and continuously flush changes to the file. Flushing to file happens if the buffer is filled, forced flush every 1 second, or if Gor is closed. You can change it using `--output-file-flush-interval` option. It most cases it should not be touched. ### File format -HTTP requests stored as it is, plain text: headers and bodies. Requests separated by `\nšŸµšŸ™ˆšŸ™‰\n` line (using such sequence for uniqueness and fun). Before each request goes single line with meta information containing payload type (1 - request, 2 - response, 3 - replayed response), unique request ID (request and response have the same) and timestamp when request was made. An example of 2 requests: +HTTP requests stored as it is, plain text: headers and bodies. Requests separated by `\nšŸµšŸ™ˆšŸ™‰\n` line (using such sequence for uniqueness and fun). Before each request goes single line with meta information containing payload type (1 - request, 2 - response, 3 - replayed response), unique request ID (request and response have the same), timestamp when request was made (in nanoseconds) and latency (time difference between request start and finish. For `request` is always zero). An example of 2 requests: ``` -1 d7123dasd913jfd21312dasdhas31 127345969\n +1 d7123dasd913jfd21312dasdhas31 1710781031501207115 0\n GET / HTTP/1.1\r\n \r\n \n šŸµšŸ™ˆšŸ™‰ \n +1 a1ba0050a213128487cd25db 1710781031551256751 0\n POST /upload HTTP/1.1\r\n Content-Length: 7\r\n Host: www.w3.org\r\n @@ -102,4 +103,4 @@ You can loop the same set of files, so when the last one replays all the request Pass `--input-file-loop` to make it work. *** -You may also read about [[Capturing and replaying traffic]] and [[Rate limiting]] \ No newline at end of file +You may also read about [[Capturing and replaying traffic]] and [[Rate limiting]]