Closed
Bug 150222
Opened 22 years ago
Closed 22 years ago
"document contains no data" sucks sometimes
Categories
(Core :: Networking: HTTP, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: Matti, Assigned: darin.moz)
References
()
Details
Attachments
(1 file)
(deleted),
text/plain
|
Details |
win2k build 20020606.. (trunk)
connection: A-DSL(768/128 kbit) without proxy, firewall
I get often a "document contains no data" popup on this forum.
Many (!) people see this at this server. (with Rc1, Rc2, Rc3, 1.0)
I saw this warning 10x in a half hour reading and i saw that mozilla tries to
connect 3x in the status bar and finaly displays the warning.
I dunno if related:
There are also problems if you post something and you often get 3x the same post.
From forum-users : This seems to be a win32 problem.
possible dupe of bug 139879..
Reporter | ||
Comment 1•22 years ago
|
||
The log is very long because it's difficult to reproduce the problem.
I got the error and i closed the browser directly after the warning.
(should be easy to find at the end of the log)
Reporter | ||
Updated•22 years ago
|
Summary: "document conatins no data" sucks sometimes → "document contains no data" sucks sometimes
Assignee | ||
Comment 2•22 years ago
|
||
matti: thx for the http log.
Status: NEW → ASSIGNED
Priority: -- → P3
Target Milestone: --- → mozilla1.1beta
Comment 3•22 years ago
|
||
I have the same problem (with Moz 1.0 and win 98), but it isn't limited to the
forums.
I also saw the "document contains no data" error an other pages on the server
www.chip.de, for example when I read the news.
Assignee | ||
Comment 4•22 years ago
|
||
> There are also problems if you post something and you often get 3x the same
> post.
yikes! that's really bad... the problem is likely related. if moz discovers a
closed socket connection after writing a request, it'll open another connection
and rewrite the request automatically. the assumption being that the server
never completed the transaction (it's supposed to give a response to ever HTTP
request).
this problem is therefore either a bug in the way we determine a prematurely
closed connection or a bug in the server. i'm tempted to blame this on the
server, but that's probably just wishful thinking ;-)
Assignee | ||
Comment 5•22 years ago
|
||
unfortunately the log file doesn't reveal anything interesting. it just says
that moz restarted one of the GET requests 10 times and then gave up. for
whatever reason the server never provided any content in response to the GET
request(s).
it might be interesting to spend some time on this website with NS4.x ... it has
similar logic in place and also has its own "the document contains no data"
dialog. i wonder if you'd ever see that dialog while using 4.x?
Assignee | ||
Updated•22 years ago
|
Target Milestone: mozilla1.1beta → ---
Assignee | ||
Comment 6•22 years ago
|
||
untargeted until we get some traction on this...
Reporter | ||
Comment 7•22 years ago
|
||
i tried it again:
5min with Mozilla : document contains no data
40min NS4.7x : no error
30min IE5.01 : no error
Is there something that i can provide ?
I have this same problem at
http://www.vauva-lehti.fi/keskustelut/luettelo.asp?group=32
( It is a Finnish forum, so you propably won't understand a word in there )
However the popup warning doesn't appear every time. ( never on IE ).
I think it has something to do with the fact that the asp page has to be created
every time I try to fetch it with Mozilla. That takes time. How much time, that
depends what the load is on the server. Perhaps the timeout time should be set
into a bit longer time?
I also have had the problem that when I posted a message to there, it appeared 9
times on the server. And after that came the same annoying message "document
contains no data"
Assignee | ||
Comment 9•22 years ago
|
||
reijo: sounds like you are seeing bug 168138.
Comment 10•22 years ago
|
||
Dupe of bug 135182 ?
Reporter | ||
Comment 11•22 years ago
|
||
wfm with latest CVS
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•