It seems that the fogBUGZ integration does not respect the Vault client proxy settings. I can successfully update a bug via vault when I'm in the office (no proxy). It fails when I am at my client's office's (proxy). Vault and fogBUGZ both work independently in both locations but the integration only functions when I'm not behind a proxy server.
Therefore I suspect that fogBUGZ integration does not respect the Vault client proxy settings
Can you confirm that this is the case?
fogBUGZ integration does not respect the Vault client proxy
Moderator: SourceGear
-
BrianSchmitt
- Posts: 5
- Joined: Wed Oct 06, 2004 1:43 pm
-
BrianSchmitt
- Posts: 5
- Joined: Wed Oct 06, 2004 1:43 pm
Vault client does not respect the proxy setting
Ok, that is working now - BUT. It seems that the Get Repository List button in the Edit Profiles dialog also suffers from this malady as well - even in version 3.0.2 (2812).
-
BrianSchmitt
- Posts: 5
- Joined: Wed Oct 06, 2004 1:43 pm
Correct.lbauer wrote:Ok, we'll take a look at this. So when you try to edit a profile, there's an error in getting the repository list?
Also I'm trying to use the command line client today without success, needless to say I'm suspicious that the proxy is a problem here as well. I cannot seem to find any documentation that indicates where one would put the proxy info when using the command line. My guess is that's not supported, yet.
