Posts: 37
Joined: 16.Dec.2003
From: Upstate NY
Status: offline
Hey! I'm trying to gather some best practices and experiences people have when websites require Javascript and it doesn't work well through the proxy. We have numerous occasions where yet another website attempts to run a Java application and it fails, for reasons we have a hard time figuring out. We corrected the issue on ISA 2000 regarding authentication problems, and carried that rule over into our ISA 2004 array, but we still run into the occasional road block. Applications just fail now and again. It seems to be a recurring issue, but I see very little posted here, so I assume everyone has either mastered it, or they never hit Java applications on websites! Any thoughts would be appreciated. Thanks, Gary
For those sites, you need to configure them for Direct Access. Its a problem encountered for all Web proxies when connecting to Java sites that aren't coded to support authenticating or HTTP 1.1 compliant Web proxies.
quote:Originally posted by gary1218: Hey! I'm trying to gather some best practices and experiences people have when websites require Javascript and it doesn't work well through the proxy. We have numerous occasions where yet another website attempts to run a Java application and it fails, for reasons we have a hard time figuring out.
hi gary, first of all, javascript and java are completely different
second: I HATE java (not javascript) in everyone of his manifestation
Posts: 37
Joined: 16.Dec.2003
From: Upstate NY
Status: offline
In ISA 2004, I've created a rule that sits at the top of the list. It contains IP addresses and some URL's of websites that require direct access for Java purposes. I set the rule to allow access to "All Users" (which is essentially "anonymous", i.e. not requiring authentication) to these sites. That corrects the issue with Java that fails authentication.