RE: proxy server

OK.  Sorry if my pessimism was a bit overboard.
Years of software development has changed me
in two ways, neither of which are positive
traits:

1.  Lots of gray hair

2.  The occasional assumption that if I don't
regularly use something, then it doesn't work. 

--
Eric Sink
Software Craftsman
http://software.ericsink.com/
 
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Metro Sauper
Sent: Wednesday, January 07, 2004 10:09 AM
To: [email protected]
Subject: RE: [vault-list] proxy server

We use the following configuration:
 
client -> ISA server -> NAT Router -> {internet} -> NAT Router -> Vault
Server
 
The Vault Server is also an ISA server for the rest of the office network.
The actual Vault SQL database is on a server behind the Vault Server.
 
We only allow secure (https) connections to the vault application on the
server.
 
We have never had a problem with this setup.  I've never even considered
that it might not work.  Isn't one of the main reasons for using the http
protocol to take advantage of the in-place enterprise infrastructure support
for it?
 
 
Best regards,
 
Metro.
 
-----------
Metro T. Sauper, Jr.
President
Sauper Associates, Inc.
221 County House Road
Suite D
Sewell, NJ  08080
 
V: 856.228.5300
F: 856.228.2311
 



________________________________

	From: [email protected]
[mailto:[email protected]] On Behalf Of Steven Buxton
	Sent: Wednesday, January 07, 2004 10:25 AM
	To: Eric Sink; [email protected]
	Subject: RE: [vault-list] proxy server
	
	
	I access mine through an ISA proxy.  Most of the time my enviro
looks like Client -> ISA -> Router -> ISA - Vault.  Works like a champ.
Never had any issues.
	 
	Steven
	
	
________________________________

	From: [email protected] on behalf of Eric Sink
	Sent: Wed 1/7/2004 9:42 AM
	To: [email protected]
	Subject: RE: [vault-list] proxy server
	
	

	
	Hmmm.  I am having two reactions to your note:
	
	First, I'm surprised that this is working at all.
	
	Second, I'm curious why you are getting that
	particular symptom.
	
	But mostly, I'm just surprised that it works at
	all with a proxy server.  Is anyone here actually
	using Vault regularly with a proxy server?  IIRC,
	this is not something we would consider a
	"supported" configuration.
	
	Anyway, as to your actual problem:  I don't suppose
	there is something in your proxy server which is
	configured to timeout sockets after one minute?  ;-)
	
	AFIAK, there is no timeout in Vault which is 60
	seconds long.
	
	--
	Eric Sink
	Software Craftsman
	http://software.ericsink.com/
	
	-----Original Message-----
	From: [email protected]
	[mailto:[email protected]] On Behalf Of Brett A
Hoover
	Sent: Tuesday, January 06, 2004 4:45 PM
	To: [email protected]
	Subject: [vault-list] proxy server
	
	I have Vault set up on a port other than 80.  Everything is working
	correctly except when I'm on site at a vendor where they use a proxy
	server.
	
	In order to get Vault to function correctly, I need to start up
Vault,
	then fire up IE (with proxy enabled) and hit 
	http://myurl:port/VaultService/VaultService.asmx -- which loads
fine. 
	Then I am able to login to Vault.  Without doing this, Vault refuses
the
	connection.
	
	Additionally, after a minute, any additional request to Vault gives
me
	the error message  that Vault couldn't perform the action.  My
	connection to the server may have timed out.  I go to browser,
refresh
	the page, then retry the operation and everything works fine.
	
	Despite it working, it is very annoying to have to refresh a web
page
	before performing a Vault operation.  And note, that the time out
can be
	less than a minute.
	
	Any ideas/suggestions would be greatly appreciated.
	
	Thanks
	
	Brett
	
	_______________________________________________
	vault-list mailing list
	[email protected]
	http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list
	
	_______________________________________________
	vault-list mailing list
	[email protected]
	http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list