setting header in websphere 8.

I am sure this problem is very common. I have excel export functionality on my application. I am using Websphere. The export doesn't work on IE8 when on SSL. I searched on internet. I found that WAS sets a header "Cache-Control: no-cache". So because of this IE8 won't allow you to download the excel file. I saw some solutions where people say set header in some servlet filter. But it doesn't work. Then I saw one solution which says as below:

We found that each instance of a response.addCookie() call causes the
“no-cache…” to be added to the Cache-Control header. 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.

A silly solution to a silly, undocumented problem (feature).”

Looks pretty simple. But I am not sure how do I know that cookie processing is completed? Can any one help me on that?

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?

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?

I don't remember exactly but I know I changed between Content-Disposition values I think I tried inline and it worked. You can give it a try.