F
Frank Lorenz
Hi
A servlet generated response is treaten differently each time. One time the
webbrowser raises correctly a download dialog, wich enables the user to save
a file. This happens when the data to download is small. The other time,
instead to show a download dialog, the webbrowser shows the data directly as
a new page. This happens with larger downloaddata.
Therefore i suppose it depends on wrong caching adjustments i've made in the
responseheader. But i'm not really shure about it. The header is configured
in a way, that the response is declarated as extreme volatile, so that the
caching mechanism actually will not grip.
The header looks like:
header("Content-disposition: attachment; filename=file.csv");
header("Content-type: application/octet-stream");
header("Pragma: no-cache");
header("Expires: -1");
The problem occurs with any webbrowser (doesn't matter if ie, ns,
mozilla...). Tomcat 4.0.x is used.
Regards
the clueless Frank
A servlet generated response is treaten differently each time. One time the
webbrowser raises correctly a download dialog, wich enables the user to save
a file. This happens when the data to download is small. The other time,
instead to show a download dialog, the webbrowser shows the data directly as
a new page. This happens with larger downloaddata.
Therefore i suppose it depends on wrong caching adjustments i've made in the
responseheader. But i'm not really shure about it. The header is configured
in a way, that the response is declarated as extreme volatile, so that the
caching mechanism actually will not grip.
The header looks like:
header("Content-disposition: attachment; filename=file.csv");
header("Content-type: application/octet-stream");
header("Pragma: no-cache");
header("Expires: -1");
The problem occurs with any webbrowser (doesn't matter if ie, ns,
mozilla...). Tomcat 4.0.x is used.
Regards
the clueless Frank