Re: IE 8 loses last tag(s) and displays </ at bottom of page
It depends on the web server, and if it's a true stream or just buffered
content. If it's buffered, most web servers will add the Content-Length
header themselves. If there's no header, the browser will just accept the
data until the connection is closed, so this shouldn't cause you any
problems unless your application never closes the TCP socket after sending
"Martin Kultermann" <MartinKultermann@discussions.microsoft.com> wrote in
> Thanks a lot Dan, I think this is solved.
> I was writing the client response stream to a file as well to help with
> The length of that file reported by Windows, the Content Length that I
> placed into the response header and the body size reported by Fiddler are
> exactly the same.
> Then I tried removing the Content Length header to see if that makes a
> difference and it did, it now seems to work.
> I was under the impression that performance would suffer if you did not
> specify a content length, because the client would not know when the
> is done or might wait for more. Do you know if that's true?
> "Dan" wrote:
>> "Martin Kultermann" <MartinKultermann@discussions.microsoft.com> wrote in
>> message news:1426A9E7-F0AB-4450-A97A-4FC7433B1DA8@microsoft.com...
>> > Hi everyone, I have a java web app that generates HTML pages and sends
>> > them
>> > to IE 8 clients.
>> > The HTML appears to be well formed and includes all required ending
>> > tags
>> > and
>> > I have verified that the entire HTML stream is flushed to the client
>> > and
>> > that
>> > the proper content length is set in the response headers.
>> > On some pages, the client page seems to cut off somewhere near the end
>> > of
>> > the HTML (sometimes within a hidden input definition or usually within
>> > the
>> > trailing </html> tag.
>> > The view source shows me that the end of the html is missing which
>> > explains
>> > why the </ appears at the end of the page.
>> > It does not happen on every page and I have been unable to determine
>> > the
>> > pattern that makes it happen.
>> > Any ideas on what may be causing this or where to look will be greatly
>> > appreciated.
>> > Cheers
>> > Martin Kultermann
>> > eStar Communications
>> You're going to have to look at tracing the underlying data packets and
>> if there's a problem there, IE will just render what is has been sent.
>> guessing that the Content-Length will be off slightly - you may think
>> correct, but if you're sending any unicode characters and not taking into
>> account double bytes, for instance, you could be a few bytes off on your
>> length calculation.
>> Try something like Fiddler2 http://www.fiddler2.com/fiddler2/ and look
>> the response data headers and content for these requests.