This content has been marked as final. Show 6 replies
Could you set debug level to message and look into the Gateway_from_to_Server resp. Gateway_from_to_Browser debug log?
The User-Agent header should be listed there.
Did anyone find the solution for this problem?
I'm having the exact same problem.
I've checked the Java Code of the Application, and it searches for the string 'Gecko' and 'MSIE' to return the correct file. If none of those is found, the IE file should be returned.
When I launched a packet tracer on the application server, I noticed no differences in the HTTP requests, the User-Agent header was left unchanged.
The weirdest thing is: this setup has always worked, but suddenly it stopped working, altough nothing was changed in the portal or in the application.
The only thing that was changed are the proxy servers: could this be caused by a proxy server?
Thanks in advance.
I've read in the docs that caching can be disabled, but it looks to me that it would disable ALL caching and not just caching for a certain URL. Is there a way for telling the gateway that it should not cache the contents retrieved from a certain URL (e.g: the file "http://myserver.com/app/js/foo.js" should never be cached).
Or is there another workaround (the HTTP request keeps adding the "If-Modified-Since" header, which causes a response of "304 Not Modified")?
Or should I be doing this on the webserver of the application: adding some kind of "Cache-Control: no-cache" header?
Disabling the cache on the proxy servers managed the trick for me.