nutterthanos
nutterthanos
@pimterry strange this bug has not happened again since i turned off any breakpoints i had on
@pimterry to be fair tho the current data is already in memory anyways that was already received from the websocket so i guess the fix would be if it drops...
the trigger i noticed is on http2 requests if i have an breakpoint on such an request like for example on play-fe.googleapis.com or one of its requests or something best...
Also note that with certain rules in place it should still prevent certain other rules being used on it anyway like force close connection/time out connection etc being used with...
> I think the real solution is support for this within https://github.com/httptoolkit/httptoolkit/issues/76. You should be able to select multiple requests directly, and then click 'Download all response bodies' and get...
There is closer to an more recent updated library that can kinda do what is required but that's like not nodejs sadly https://github.com/libwbxml/libwbxml again I assume this will be like...
couldn't we store the data for each request like in an .tmp file or something in for windows %temp%\httptoolkit\* but then in case of an crash like so we would...
> While running the script with -allPages parameter, the scripts don't seem to go to the next page; so it keeps calling the first page and then stop at 1000...
> I use this once per month (on MSFT's patch Tuesday). This month, it is not working for me either. > > I am using a Search that returns 28...