Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Pity you didn't implement HTTP::Proxy using POE. No need to fork, better portability ...
    --

    Ilya Martynov (http://martynov.org/ [martynov.org])

    • Yeah, yeah, I've been told that several times. :-)

      I'd like to work on a POE::Component that would do what HTTP::Proxy does. It's just that I was too lazy to learn POE. And I have so much to do until HTTP::Proxy is actually usable for more than simple HTTP requests to HTTP::Proxy (the filtering system is the most exciting part of HTTP::Proxy, and it need some more work, and a decent API). So I guess this will happen, but only later, someday.

      I'll soon add the capability to answer CONNECT requests (based on my experience with connect-tunnel [cpan.org]). I bet that using Crypt::SSLeay and HTTP::Proxy one could create a simple man-in-the-middle attack based on the fact that nobody really cares about the certificate they are sent. That is, assuming people would use such a proxy (for example, if they are lead to believe it is an open proxy [google.com]).

      • Beware that POE is likely to require very different design of API (because it must be event based). If you decide at some point to port HTTP::Proxy to POE this port will not straight-forward.
        --

        Ilya Martynov (http://martynov.org/ [martynov.org])