Oops, I should have clarified this. Once the file transfer is complete, we send
a response.sendRedirect(filename). At this point, the file is handling client
side
by the browser, the content disposition is no longer pre-determined, but
handled
depending on the users MIME settings.
"Christopher K. St. John" wrote:
> Filip Zalewski wrote:
> >
> > In light of the aformentioned issue with IE, building an output
> > stream to send the data is now technically unfeasible.
> >
>
> Ok, IE bug, can't send the data using a content-disposition
> header. Got you so far. But after that, I'm not sure I
> understand: you're moving the document out into an area
> where your web server can see it and then what, exactly?
> How does the client get the document? If the web server
> manages to send back an acceptable stream of bytes, why
> can't the servlet send back the exact same sequence of
> bytes? Or have I misunderstood your explanation?
>
> --
> Christopher St. John [EMAIL PROTECTED]
> DistribuTopia http://www.distributopia.com
>
> ___________________________________________________________________________
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources: http://java.sun.com/products/servlet/external-resources.html
> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
