Environment
Novell iChain 2.3 Support Pack 4
Novell iChain 2.3 Support Pack 3
iChain 2.3 build 2.3.214
Situation
Web server IP address defined for accelerator changing on a regular
basis in a development environment. This is because the web
developers have test web servers and code on laptops. Whenever
these developers are assigned new IP addresses, the iChain services
accelerating these laptops return 504 gateway timeout errors.
This problem occurs with or without formfill, rewriter, OLAC, authentication and authorization services enabled.
This problem occurs with or without formfill, rewriter, OLAC, authentication and authorization services enabled.
Resolution
Fixed with Access Manager 3.0.
The workaround in place for iChain is to create a NAS file that an administrator can FTP to the iChain miniFTP server and execute. This nas file would simply run the following two commands:
purgecache
apply
After the FTP session is established to the iChain miniFTP server, one simple does a put filename.nas filename.nas,execute to automatically execute the contents of the filename.nas file. With this workaround, the web developer could purgecache whenever his web server IP address changed to avoid getting 504 errors.
The workaround in place for iChain is to create a NAS file that an administrator can FTP to the iChain miniFTP server and execute. This nas file would simply run the following two commands:
purgecache
apply
After the FTP session is established to the iChain miniFTP server, one simple does a put filename.nas filename.nas,execute to automatically execute the contents of the filename.nas file. With this workaround, the web developer could purgecache whenever his web server IP address changed to avoid getting 504 errors.