Keep Coding

I have a local artifactory repo, I can talk to the repo just fine from local and jenkins running on another vm. I recently setup a slave for jenkins, everything appears to work fine, except when it comes time for maven on the slave to talk to my artifactory repo, all hell breaks lose, I've narrowed it down to this
[INFO] artifact org.eclipse.core:resources: checking for updates from myrepo
[DEBUG] Using Wagon implementation lightweight from default mapping for protocol http
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
[DEBUG] Connecting to repository: 'myrepo' with url: 'http://myrepo/repo/'.
[DEBUG] Using Proxy: <some ip address>
[DEBUG] Using Wagon implementation lightweight from default mapping for protocol http
[INFO] artifact org.eclipse.core:resources: checking for updates from jibx.sf.net
[DEBUG] Using Wagon implementation lightweight from default mapping for protocol http
[DEBUG] Checking for pre-existing User-Agent configuration.
[DEBUG] Adding User-Agent configuration.
The reason why im doing all this is because i noticed the slave is really slow in downloading dependencies, my guess is there is something wierd going on between proxy/redirecting. I turned off proxy but it's still trying to use it? I used -U flag but no dice, it's caching the configuration somewhere unkown...
What is wagon implementation for mapping http protocol?
What is the user-agenmt it's checking for?
Where is it finding it and why is it using it?
Oh so many mysteries...