Start trace the traffic : curl --location --request PUT '0.0.0.0:8080/proxy/8081/har?captureHeaders=true&captureCookies=true&captureContent=true&captureBinaryContent=true&initialPageRef=MyPage%20112&initialPageTitle=My%20Page' \ --header 'Content-Type: application/x-www-form-urlencoded' \ --data-raw ''
Use user agent of your choice, in my case chrome, configure it to use created proxy( either throught system proxy or with args if user agent support it, chrome supports it so I will rpovide here command for OSX) open -a "Google Chrome" --args --proxy-server="http://0.0.0.0:8081" --profile-directory=Default5
Also one can use postman and set in setting to use created proxy
Open this web page https://www.wsj.com/ or curl --location --request GET 'https://wsj.com'
Actual result: page is not loaded and in proxy console there is and exception that I put in description:
Expected behavior
Page is loaded same way as without this empty response filter, no exception happen, at least option to set size in standalone mode.
Describe the bug Сaught an exception on ProxyToServerConnection In standalone mode I got Response entity too large when enable filter:
I see there is same issue for browsermob and comment from @ericbeland with link here https://github.com/browserup/browserup-proxy/issues/77. But workaroun there is for embedded mode.
To Reproduce Steps to reproduce the behavior:
./browserup-proxy-2.0.1/bin/browserup-proxy -port 8080
curl --location --request POST '0.0.0.0:8080/proxy?trustAllServers=true&port=8081'
curl --location --request POST '0.0.0.0:8080/proxy/8081/filter/response' \ --header 'Content-Type: text/plain' \ --data-raw 'response'
curl --location --request PUT '0.0.0.0:8080/proxy/8081/har?captureHeaders=true&captureCookies=true&captureContent=true&captureBinaryContent=true&initialPageRef=MyPage%20112&initialPageTitle=My%20Page' \ --header 'Content-Type: application/x-www-form-urlencoded' \ --data-raw ''
open -a "Google Chrome" --args --proxy-server="http://0.0.0.0:8081" --profile-directory=Default5
Also one can use postman and set in setting to use created proxyhttps://www.wsj.com/
orcurl --location --request GET 'https://wsj.com'
Actual result: page is not loaded and in proxy console there is and exception that I put in description:
Expected behavior Page is loaded same way as without this empty response filter, no exception happen, at least option to set size in standalone mode.
Please complete the following information: