> What if you use, say, text/plain (assuming the content is compatible
> with the type and the UTF-8 character encoding) or application/octet-
> stream? From what you say above, it seems you get this problem no
> matter what the content type, which suggests the problem might be
> with how you generate the response on the server. Have you tried to
> monitor the network traffic to rule out the possibility of, say, that
> the server just sends content forever? Do you not get any alert(), or
> just not the desired one?


I get a couple of alerts then 100% CPU. The server is not sending
content forever. I tried with a simple 5 line JSP page, same problem.

text/plain seems to work fine. I also tried:

text/plain; boundary=asdasdas

This exhibits the same problem. It seems to me that if IE has any idea
that it is a multipart response (because of a 'boundary' in the
Content-Type or because of a 'mulitpart') that it has issues. If it
doesn't think it is multipart it has no issues. I would guess this has
something to do with the way IE tries to look at responses to determine
what type they are, both the headers and the content.

I can work around by just sending the content as text/plain or
something like that. I don't send any preamble with the multipart
response so the first --xxxxx should be the boundary, so I can live
without the boundary in the header itself.