Complex pages exceed log window buffer?

[JJoe]

(Oct. 17, 2010 11:16 PM)Aljan Darkmoon Wrote:  

(Oct. 17, 2010 08:50 PM)JJoe Wrote:  You may be able to use the Proxomitron to stop loading at a specific spot.

Abort button? Special filter? Not sure what you have in mind...

An expression like

Code:

$SET(StopIt=$DTM(c))$TST(StopIt=[#nnn:*])$RDIR(http://local.ptron/killed.gif)

used in a filter or list. "nnn" is the connection number that you wish to stop at. The browser will probably make request beyond "nnn" but the Proxomitron will redirect all requests after "nnn".

(Oct. 17, 2010 11:16 PM)Aljan Darkmoon Wrote:  

JJoe Wrote:Loading just one file and then viewing the log may help.

By 'file', do you mean 'link', as in "go to http://local.ptron/.pinfo/urls/ , go down the list of addresses that the test page (the one I'm trying to log) loaded, load one address at a time and view the log for each"?

Sort of, my hope is that you don't need to examine every request. Also, you may have to fake some data to make the server reply but I didn't say I had the solution.

(Oct. 17, 2010 11:16 PM)Aljan Darkmoon Wrote:  

JJoe Wrote:All the addresses may be found in http://local.ptron/.pinfo/urls/ .
MaxCapURL in the cfg file can increase the number of addresses shown.

That will help, but I also need to see URL-killer filter matches to find out if anything essential is being blocked. /k-killed connections apparently do not show up in the list of addresses (I just tested that out on a couple of pages that link to domains I have blocked).

\k redirects to a "local.ptron" address and "local.ptron" addresses do not show in http://local.ptron/.pinfo/urls/.
However, assuming that Proxo is listening on port 8080, "local.ptron" resolves to 127.0.0.1:8080. Redirects to 127.0.0.1:8080 do show in http://local.ptron/.pinfo/urls/.
So, if you're willing to modify your set.

HTH

http://127.0.0.1:8080/proxylogo.jpg