mIRC with active SOCKS/HTTP proxy settings makes FiSH stop working

[flakes]

Found by December. Not sure to what extent we can fix this.

More explanation:

<jarod> flakes to be sure:
<jarod> home > ssl proxy > irc bouncer, fish10 does not work yet?
<jarod> ah thats sock5 i guess, so no worky
<flakes> yeah no worky on socks
<jarod> why?
<jarod> cant just copy old fish code? :P
<flakes> uhm
<jarod> or is it a mirc 7 thing?
<flakes> the old FiSH used to modify the mirc.exe file
<flakes> so it hooked in before the point where a proxy came into play
<jarod> ahyes
<flakes> I don't want to modify the exe file for each new mIRC version
<jarod> is it fixable?
<flakes> so I hook in later
<flakes> at which point I have to decide for every connection whether it's IRC, DCC, HTTP, $sockopen...
<flakes> ...and proxied connection look a lot different
<jarod> i see
<jarod> well i cant use it with
<flakes> so yes it is fixable, but it's a substantial amount of complexity to overcome
<jarod> ssl proxy > random ssl proxy > server > irc
<jarod> i guess when $sockopen is done, all beyond that should be good?
<flakes> mIRC > server > whatever and mIRC > bouncer > whatever works
<flakes> uhm no
<flakes> that's all working
<flakes> just proxies aren't, because those connections ARE IRC connections (where $sockopen etc. aren't)
<flakes> that's the hard thing to determine
<jarod> ya ok, but its a local proxy
<jarod> port 127.0.0.1
<jarod> err
<jarod> host
<flakes> doesn't matter
<flakes> on a normal IRC connection, the very first thing that goes over the wire is always "CAP LS" ... when SSL is used, another bit of data comes before that, but that's easy to recognize
<flakes> however, when a proxy is used
<flakes> it's the proxy protocol that encapsulates IRC. Or, even worse, proxy protocol encapsulates SSL which encapsulates IRC
<jarod> ah
<jarod> ok ok

[flakes]

Implemented/fixed for the next version. Yay!

[Weyland]

Great news! Been waiting for this to work ever since 2010. Wonderful.