02-21-2002 09:08 AM
Hi All,
I'm experiencing problems using the "outgoing proxy" feature with a content engine running ACNS 4.03.
When this feature is enabled, it takes a long time to get the "execute or save to disk" popup window in the web browser, but when I get it, the file is downloaded in a few seconds.
It seems like the CE waits for the file to be completely retrieved before delivering it to the client...
This is not service impacting when this is a small file, but when the file is bigger than 1MB, the browser fails with a timeout.
Can anyone help ?
Thanks,
Phil.
02-28-2002 01:40 PM
It's likely that the link between CE and outgoing proxy is slow or the outgoing proxy itself has some problem. If you can, ping/traceroute to outgoing proxy; request via the configured outgoing proxy directly from your browser to get an idea.
If you verify that those are not issues, you may do a "show stat http proxy outgoing" on CE and see if the stats are dominated with failures instead & if so, then it's time to call TAC.
BTW, which build of ACNS4.03 are you running? Did it happen on IE or Netscape or both?
03-08-2002 09:33 AM
4.01b1 code had a hardcoded proxy timeout value of 300 micro seconds. The ability to set this value was introduced in 4.03 to address symptoms like the one you are describing when the CE is not able to connect to its upstream proxy within this time constraint. (also documented the following bug : CSCdv36226 - "Need CLI to configure connection timeout for outgoing proxy"
The fix was implemented with the addition of the follwoing command to set this value: 'http proxy outgoing connection-timeout' command:
590(config)#http proxy outgoing connection-timeout ?
<200-5000000> Timeout period for probing outgoing proxy servers in microseconds
590(config)#
I hope this helps!
Cheers,
Perry.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide