Hi,
I don't know the exact place where I have to post this, so
I am posting here.
The website has a link button (server side control)
which writes (sends) the contents file as a attachment. The file which
needs to be send will change frequently and the name of the file will
be determined in the run time (may change even for successive clicks).
The problem is the web server is configured to work in SSL (HTTPS) and a
BigIP layer sits in between the client and server and monitors the load
balance and also act as proxy.
When the responds sends the file
to the client (through Response.Write with the required MIME header to
say that the response contains a attachment), the response is cached in
the proxy (BigIP ) and when the user clicked the link second time, it
opens the file directly in browser instead of opening it as file
download.
We tried with Respons.Cache.SetCacheability(HttpCacheability.ServerAndPrivate), but no help.
We tried with Pa ...
Go to the complete details ...