MM 2.3 Beta 2 doesn't use the proxy settings for amazon
Moderator: Gurus
MM 2.3 Beta 2 doesn't use the proxy settings for amazon
I am at work behind a firewall. The CDDB one works, I was expecting they would both use the same settings.
proxy problems with auto-tag from Amazon
I just tested this using several open proxies on ports 80 and 3128 and could not detect any problem -- in all cases Internet Explorer's proxy settings _were_ used by the embedded browser in the auto-tag from Amazon dialog.
If you have any more information that might help to reproduce the problem, let me know.
-Rusty
If you have any more information that might help to reproduce the problem, let me know.
-Rusty
I have an authenticating proxy at work. That means I have to log in on each web access.
So, by default that would mean that IE settings won't work, since they don't have a login setting. To get around this with most applications that use the IE settings, I have Proxomitron set up as a local proxy. IE then points to localhost, localhost is proxomitron, which automatically logs in with my login/password to the real proxy.
This works with all apps that actually use the IE proxy settings. So, if MM is in fact getting them from IE, it is doing something differently.
If there are already settings in the CDDB settings for the proxy, why have the amazon portion work differently?
So, by default that would mean that IE settings won't work, since they don't have a login setting. To get around this with most applications that use the IE settings, I have Proxomitron set up as a local proxy. IE then points to localhost, localhost is proxomitron, which automatically logs in with my login/password to the real proxy.
This works with all apps that actually use the IE proxy settings. So, if MM is in fact getting them from IE, it is doing something differently.
If there are already settings in the CDDB settings for the proxy, why have the amazon portion work differently?
I cannot help more for now, we will try to investigate this further (possibly try with Proxomitron installed). The fact is that noone has reported this yet and there are users that use MM proxy settings similar way without any problem (e.g. for local access to Freedb using an application discussed elsewhere here in forums).
Jiri
Jiri
New data point - it seems that the freedb proxy settings are used by both, but seems to require a login and password regardless if the proxy requires one.
If I use the actual proxy address , and I specify my proxy login and pass, then it works fine.
If I use proxomitron at localhost:8080 as the proxy, it fails unless I specify a login and password, even though it doesn't require one.
So the bug is not that it doesn't work via a proxy, it is that it doesn't work without passing login and password.
If I use the actual proxy address , and I specify my proxy login and pass, then it works fine.
If I use proxomitron at localhost:8080 as the proxy, it fails unless I specify a login and password, even though it doesn't require one.
So the bug is not that it doesn't work via a proxy, it is that it doesn't work without passing login and password.
proxy problem
jmaver,
In testing this, I found that MM definitely uses the IE proxy settings (not those of freedb).
I'm beginning to think that this might be related to proxomitron (perhaps it uses a single set of proxy settings per application).
Regardless, it sounds as if this is working for you now, and it's probably something that we can look into post-release.
-Rusty
In testing this, I found that MM definitely uses the IE proxy settings (not those of freedb).
I'm beginning to think that this might be related to proxomitron (perhaps it uses a single set of proxy settings per application).
Regardless, it sounds as if this is working for you now, and it's probably something that we can look into post-release.
-Rusty