github/goreplay
4
0
Fork 0
mirror of https://github.com/buger/goreplay.git synced 2024-04-21 12:32:02 +00:00
Code Issues Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Leonid Bugaev
2015-07-12 08:52:59 +05:00
parent becb4b958f
commit f1c341e2ac
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+5 -1
View File
@@ -349,6 +349,10 @@ Basic idea is that SSL was made to protect itself from traffic interception. The
More can be find here: https://github.com/buger/gor/issues/85
# Is there a limit for size of HTTP request when using output-http?
Due to the fact that Gor can't guarantee interception of all packets, for large payloads > 200kb there is chance of missing some packets and corrupting body. Treat it as a feature and chance to test broken bodies handling :)
The only way to guarantee delivery is using `--input-http`, but you will miss some features.
### I'm getting 'too many open files' error
Typical linux shell has a small open files soft limit at 1024. You can easily raise that when you do this before starting your gor replay process:
@@ -397,4 +401,4 @@ To achieve the top most performance you should tune the source server system lim
* [3SCALE](http://www.3scale.net/)
* [Optionlab](http://www.opinionlab.com)
* [TubeMogul] (http://tubemogul.com)
* To add your company drop me a line to github.com/buger or leonsbox@gmail.com
* To add your company drop me a line to github.com/buger or leonsbox@gmail.com