NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Using your own agent... (Score:2)
Hi! I'm the author of HTTP::Proxy. :-) Glad you like it.
I don't think you need to define your own agent to log information. In fact, I think I should never have opened the opportunity to set your own agent. You could simply use a response filter that catches the title tag and print it in you log file.
I also don't understand your while(1) loop. The $proxy->start() is already a while(1) loop.
And you say that the proxy doesn't fork? That probably means you're running it under Win32, don't you? Alas, the forking code doesn't work very well under Windows. Also, maybe the documentation doesn't state this clearly, but you can change the engine (HTTP::Proxy::Engine subclass) by passing the engine parameter to the constructor. On Unix, I use the ScoreBoard engine. This way: my $proxy = HTTP::Proxy->new( engine => 'ScoreBoard' );
Regarding images in Internet Explorer, I'm not sure what's going on. I know for sure that HTTP::Proxy doesn't support pipelined requests (because that's what apt-get does, and it fails for the moment).
As for SSL connections, HTTP::Proxy supports the CONNECT method, but cannot look inside.
Reply to This
Re:Using your own agent... (Score:1)
I'm so glad to receive feedback from you, the very author of HTTP::Proxy.
Re: (Score:1)