aXes installs many files on the IFS in compressed format. It delivers them to the browser in this compressed form. Sometimes networks and/or browsers are unable to handle the compressed format correctly (the circumstances in which this problem occurs are arcane).
A compressed file problem is typified by a JavaScript error that says something like Line 1 character 1 is invalid - because the compressed file cannot be processed by the JavaScript interpreter.
You can confirm you have this problem by doing this simple test:
Go to the aXes home page and select this option from the menu:
Test Application Server option
from the Launch aXes Tests menu
If you cannot even display the home page use a URL formatted like this instead:
http://<aXes host and port>/echo
Scroll through the resulting display.
If the HTTP_ACCEPT_ENCODING= option is not displayed or if it does not say gzip, deflate, then you have this compression problem.
If you have the problem then you should use the aXes DECOMPRESS command against the various aXes IFS folders, the most significant one being the <axes root folder>/ts folder. After decompressing you must clear your browser caches.
Checking for network/browser compression issues
Moderator: jeanmichel
-
axessupport
- Posts: 14
- Joined: 07 Feb 2017, 10:08
Checking for network/browser compression issues
- Attachments
-
- FastCGI Echo.PNG (41.48 KiB) Viewed 10177 times