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
Currently we use Nginx ngx_mirror_module to implements mirroring of original HTTPS request and pass to other local port like 8081. So that Goreplay can capture this traffic in port 8081.
But we have a concern that the mirroring in Nginx may have an impact on system performance while pressure testing, because lots of requests might cause the mirroring also take many system resource.
So, is there any solution for GoReplay to capture the HTTPS traffic without modification on reverse-proxy nodes?
Thanks!
The text was updated successfully, but these errors were encountered:
Currently we use Nginx ngx_mirror_module to implements mirroring of original HTTPS request and pass to other local port like 8081. So that Goreplay can capture this traffic in port 8081.
But we have a concern that the mirroring in Nginx may have an impact on system performance while pressure testing, because lots of requests might cause the mirroring also take many system resource.
So, is there any solution for GoReplay to capture the HTTPS traffic without modification on reverse-proxy nodes?
Thanks!
The text was updated successfully, but these errors were encountered: