Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[KyroMaster]

When I set the HTTP proxy in aMule, is it just for fetching things from HTTP like the serverlist or is it for all traffic (which would be very cool IMO).
If it´s for all traffic, can the proxy administrator see that I´m using eMule instead of viewing HTTP pages over the proxy?

[Kry]

It's for all traffic. And probably the proxy admin can see the p2p packets.

[phoenix]

Originally posted by KyroMaster
When I set the HTTP proxy in aMule, is it just for fetching things from HTTP like the serverlist or is it for all traffic (which would be very cool IMO).

Actually, the one thing aMule does not use the proxy is for fetching serverlist... This should not be a problem, once port 80 traffic is usually free. Only ed2k traffic goes through the proxy.

Cheers!

[fulgas]

Not really

you can have a http proxy and block the 80 port, allowing the http traffic only tru the http proxy...

[KyroMaster]

That´s exactly what I have i my setup here.

[phoenix]

Well, I am not sure it will work, but could you give it a try? Do that:

$ export HTTP_PROXY=www.asdf.com:3128
$ aMule &

This is supposed to be a wx feature, but I have never really tested it. Of course asdf is nothing, use a real proxy address there, and its real port number.

Cheers!

[KyroMaster]

I testet it but it doesn´t work
Wouldn´t it be logical that when I specify a proxy all traffic is routed through it and not only the ed2k one?

[phoenix]

KyroMaster,

I agree with you, but things are not always the way they should be

We use a library called wxWdgets, and this library provides us with their platform independent version of sockets. They also have wxHTTP for accessing http. Unfortunately, it looks like they do not support proxy.

I will check their code this weekend to see if there is something we can do about wxHTTP. There is a support for this environment variable, but I have to check closer the proper way to use it.

Ed2k sockets in aMule are coded independently of wxHTTP. The correct approach would be that wxSockets had proxy support inside them. But wx developers have never showed any interest in adding this functionality to their library, not that I know of. In principle, the aMule team code could be used as a starting point, although there may be some license issues to deal first (aMule is GPL, wx is not).

In fact, the HTTP functionality you loose is not a show-stopper. You can get the server.met by hand and copy the file to the proper location. Please do that and report any problems with ed2k sockets.

Cheers!

[KyroMaster]

Ok, thanks for your help  
I know wxWidgets myself, too and sometimes I´m very dissappointed because all of the developers only implement what they need for themselves (and this is NOT true IMO for great open-source projects).
I´ll test the proxy support ASAP.