HTML page size limit

[vvlad]

Hi,

I have a page that displays results from an SQL query.
If I have up to approx. 5000 results it's OK, but if the query returns more the page is completely messed up, the results are displayed but unformated and some of the text gets lost.

I've googled but did not find anything. Could it be that there is a size limit for an HTML page after which the browser reacts in a strange manner? We only use IE6 in the intranet.

vlad

 

[ca8msm]

Why are you returning that many records on one page? There is no way a user can manually look through every single record on that page so either give them the option to limit the results, or at least let them page through them.


____________________________________________________________
Mark,
[URL unfurl="true"]http://aspnetlibrary.com[/url]

Need help finding an answer? Try the Search Facility or read FAQ222-2244.

 

[BabyJeffy]

To my knowledge there is no limit to the size an HTML page is.

I suggest you run a breaking page through the validator service (

http://validator.w3.org)

and make sure it passes (based on the doctype you are using).

Assuming it all validates, then you may have to change the way you are displaying your results. For instance, you may find that if you are displaying your results in a table, then you might want to specifically set the width of columns. You may find that if you switched to displaying the data in divs is a better way to guarantee consistent rendering.

More details please.

Cheers,
Jeff

[tt]Jeff's Blog [!]@[/!] CodeRambler

http://www.coderambler.com/

http://www.coedit.co.uk/

[/tt]

Make sure your web page and css validates properly against the doctype you have chosen - before you attempt to debug a problem!

FAQ216-6094

 

[vvlad]

ca8msm
Immediately after posting I realized this would be the first question. It's an old ASP application I've inherited and now I have to fix some bugs (including this one), without spending too much time on it. Of course limiting the results or paging is not a problem, I was just wondering where the problem is.

BabyJeffy
Thanks for the suggestions, i'll give them a go and come back with some results.


vlad

 

[ca8msm]

Also, if you take Jeff's advice about setting specific widths, it can sometimes be beneficial to set the table-layout css attribute to fixed.


____________________________________________________________
Mark,
[URL unfurl="true"]http://aspnetlibrary.com[/url]

Need help finding an answer? Try the Search Facility or read FAQ222-2244.

 

[Einstein47]

It could be a timeout issue with the IIS engine not being able to completely generate the HTML from the ASP, so it sends what it has at the time and then lets the browser try to figure out how to format it.

I would have to agree that adding some limits and possible search criteria would not only help the page but would let the users get to the data they need more quickly. Before you get slammed by putting a band-aid on a page that just needs to be rewritten, I would suggest you bring it up to your supervisors and mention "The page would work better if..." and let them know you are being thoughtful as well as trying to do a good job.

However, they might just say do it anyway - and in that case the problem is theirs, you have pointed out the problem and if they don't want to hear about it, then they get what they deserve.

Einstein47
There are no kangaroos in Austria!
[[]Starbase47.com]

 

[vvlad]

Thanks again for you thoughts.

Setting specific widths in the table did not work. And of course the breaking page can't validate, as only a part of the html file is returned. Only the "bottom" is to be seen in the browser, the first part of the page including headers and the beginning of the <table> is always missing.

I finally limited the results to 1000, as this was the easiest way to do it. And as Einstein47 mentioned, the owner of the application wants to have it this way.



vlad

 

[BillyRayPreachersSon]

If only the bottom was being returned, it sounds like you might have a rogue "document.write" statement blanking out the doc somewhere - or possibly dodgy CSS making it look as if it was blanked out.

I know you've worked around it now, but it would have been interesting to find out what the issue was.

Dan



Coedit Limited - Delivering standards compliant, accessible web solutions

[tt]Dan's Page [blue]@[/blue] Code Couch

http://www.codecouch.com/dan/

[/tt]

 

[ChrisHunt]

I think, Dan, from the way he described the <head> as being missing, that he's done a View Source and found that the top part of the source is missing, rather than just the start of the rendered page.

As Einstein47 says, that's probably an IIS issue (or maybe an asp one) - both have their own forums here where this issue might find a solution.

-- Chris Hunt
Webmaster & Tragedian
Extra Connections Ltd