Hi,
We are facing something similar issue. We need to give a progress bar for file downloads and we are thinking of using jquery.download.js
This involves setting response's header with a cookie. When we tested this on our local machine with
Tomcat it works fine.
But when we put it on Websphere it doesn't.
We can't try CookiesConfigureNoCache=false setting as getting admin access and modifying this property might be a bureaucratic nightmare.
In the link shared in above posts, i couldn't get what exactly this means "So if we just set the Cache-Control header after all the cookie processing was complete, the header would then be passed unmolested to the client".
Our code to provide an excel file as save-as is pretty simple like below. What should i change in the below to make the cookie setting work in WebSphere?