Closed Bug 139879 Opened 22 years ago Closed 22 years ago

HTTP Request causing Alert "The document contains no data"

Categories

(Core :: Networking: HTTP, defect, P2)

x86
All
defect

Tracking

()

VERIFIED WORKSFORME
mozilla1.2alpha

People

(Reporter: moied, Assigned: darin.moz)

References

()

Details

(Keywords: topembed+, Whiteboard: [adt2 RTM])

Alert "The document contains no data" in result to a request made by the browser for favicon.ico, and when the webserver does not have any favicon resulting a 404. steps to reproduce : 1.Visit above URL 2.Click on button "Start Test". 3. It will open a window loading file "testing3.html" 4. Then file "testing4.html" will be loaded automatically in child window. 5. Observe..After some brief time you will get alert "The document contains no data"
Priority: -- → P1
I don't know why i can't open above url.
Sorry about this URL, its a an internal URL, This alert can also be seen when visiting Snapfish.com on a dialup connection, login into Snapfish with a valid userid, and password, select any album, this will try to bring up all the snaps in this album, here you see a alert: document contains no data. Adding a KW:nsbeta1, topembed, Since this stopping us from performing automation testing and ref to bugscape 14377
Keywords: nsbeta1, topembed
Summary: Request made for favicon.ico causing Alert "The document contains no data" → HTTP Request causing Alert "The document contains no data"
i really can not reproduce this bug,i open a demo album,but it is not have alert
same error message unexpectedly appearing also reported in bug 140711, bug 135182, bug 140014
Dup of bug 137965 ? Fix checed in on trunk April 18 (branch Apr. 25) See http://bugzilla.mozilla.org/show_bug.cgi?id=139164#c9
Steps to reproduce - see bug 135182 comment 10. (Originally this did not generate the behviour for me, now it does every time.)
Keywords: topembedtopembed+
WFM using the 1.0.0-20020514 build under linux. i tried the bubblegum link and the steps in bug 135182 comment 10... could not repro the problem. anyone else able to repro the problem? reducing severity to major since this does not seem to be all that reproducible (anymore?!).
Severity: critical → major
Whiteboard: [need testcase][WFM]
I was still able to reproduce with build 2002051304-trunk on w98 using the bug 135182 comment 10 testcase. I went back and forward a few times, opened and closed tabs, and eventually even the ireland.com homepage gave me the 'document contains no data' dialog with no displayed content. I had http1.1, keep-alive, and pipelining all turned on. Decided to test the http networking settings: Opened tab, reloaded while the page was loading, clicked on link to the irish times, reloaded, etc. No real set pattern; just lots of reloads and clicks. * http1.0 -> could not repro the error. * http1.1 without keep-alive or pipelining -> could not repro the error. * http1.1 with keep-alive without pipelining -> could repro the error. * http1.1 with keep-alive and pipelining -> could repro the error. According to validator.w3.org, ireland.com's webserver is: Apache/1.3.24 (Unix) mod_perl/1.26
djk: thx for the extra info.
Status: NEW → ASSIGNED
Whiteboard: [need testcase][WFM] → [need testcase][adt2 RTM]
Target Milestone: --- → mozilla1.0.1
darin, the site listed in bug 135182 comment 10 is the one that we saw the multiple RST's coming back from the server when using ns6. I am not sure why it acts differently when connecting with 4.7.
*** Bug 143096 has been marked as a duplicate of this bug. ***
see bug 143096 for a reproducible test case.
Whiteboard: [need testcase][adt2 RTM] → [adt2 RTM]
I've also seen this several times with build: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0rc2) Gecko/20020510 On Windows XP and 2000. I am also using a local, ad-filtering proxy, dunno if that could affect anything.
depending on how your ad-filtering proxy works, it may cause this error to appear more often. the only way to know is to capture some network traffic on a page with blocked ads... preferrably a simple page ;-)
*** Bug 150489 has been marked as a duplicate of this bug. ***
-> 1.2alpha since i'm on vacation... i think this one can probably wait for buffy.
Priority: P1 → P2
Target Milestone: mozilla1.0.1 → mozilla1.2alpha
*** Bug 143816 has been marked as a duplicate of this bug. ***
the original testcase is WORKSFORME linux trunk 2002083005. please reopen this bug if you can repro the problem.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
verified - 09/05/02 tr - win NT4, linux rh6, mac osX
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.