Could you please consider changing your proxy server configuration from being a single application setting to a per-profile setting.
We are working in New Zealand, and connect to a Vault server in Japan. Our ISP recently set up a proxy server for us to assist with routing/performance issues. We also have an internal Vault server for testing purposes. Unfortunately the proxy server is external to our network and cannot connect to our internal testing server.
Hooking the proxy server information to the profiles would resolve this issue.
Proxy server configuration
Moderator: SourceGear
Re: Proxy server configuration
I can certainly put in a feature request for this.
The proxy is for routing out to the internet though, so internally, I wouldn't expect your clients to need one, unless they are needing to connect with an external address (which is the case with some users).
Each installation of Vault has it's own individual proxy setting, so each machine could be set. Do you have more than one user using the same Vault client? That would be the only case I can think of where each person doesn't end up with their proxy set just for themselves.
The proxy is for routing out to the internet though, so internally, I wouldn't expect your clients to need one, unless they are needing to connect with an external address (which is the case with some users).
Each installation of Vault has it's own individual proxy setting, so each machine could be set. Do you have more than one user using the same Vault client? That would be the only case I can think of where each person doesn't end up with their proxy set just for themselves.
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support
Re: Proxy server configuration
To reiterate, we don't *need* to use a proxy server to connect to our production Vault server, but our ISP set one up so they could identify our Vault traffic and modify the routing of it to improve the performance (international internet links out of New Zealand are *not* great!)
The problem is that if we configure our Vault client to use the proxy server (which we want to do as it improves the performance of our production Vault server), it means that we can no longer access our internal test Vault server.
The production Vault server is used for the source for the application we are developing, while the test Vault server is used by the application itself (we are developing a Virtual Reality product that uses Vault at the backend to manage multi-user access to the VR data).
I realise this is probably an unusual configuration, but it's what we have
Cheers,
Alistair.
The problem is that if we configure our Vault client to use the proxy server (which we want to do as it improves the performance of our production Vault server), it means that we can no longer access our internal test Vault server.
The production Vault server is used for the source for the application we are developing, while the test Vault server is used by the application itself (we are developing a Virtual Reality product that uses Vault at the backend to manage multi-user access to the VR data).
I realise this is probably an unusual configuration, but it's what we have
Cheers,
Alistair.
Re: Proxy server configuration
Ok, that makes sense. I have it logged.
F:13771
In the meantime, I'm thinking you could use a registry switcher tool to just flip the registry settings on your proxy if you want.
Those would be under:
F:13771
In the meantime, I'm thinking you could use a registry switcher tool to just flip the registry settings on your proxy if you want.
Those would be under:
- ProxyManualPort
ProxyManualServer
ProxySetting
Beth Kieler
SourceGear Technical Support
SourceGear Technical Support