Closed
Bug 156380
Opened 23 years ago
Closed 22 years ago
Noted URL Doesn't Display Fully
Categories
(Core :: Networking: HTTP, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: jbucata, Assigned: darin.moz)
References
()
Details
Attachments
(1 file)
33.54 KB,
text/plain
|
Details |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623
Debian/1.0.0-0.woody.1
BuildID: Mozilla 1.0.0
The page at the noted URL doesn't fully display. It stops immediately after the
text: "Structurally, these are quite similar. But the tree walker involves some
system programming details, while the sequence generator involves".
View Source shows nothing after that point--not even closing tags or such like.
My Netscape 4.7x at work stops at exactly the same place. IE5 at work stops at
an earlier point, which varies each time I exit and relaunch to try to view it.
I know the full text is there and available via HTTP, because I can see it
through other sites. At work today I managed to finish reading it through an
Elmer Fudd filter, which seemed to be the easiest to get real English meaning
from. (I nevew thought I'd evew use fiwtews wike this as a netwowk debugging
toow...) Searching for a suitably large chunk of text in Google finds it there,
and Google's cached copy of the page displays just fine. (Wish I'd thought of
that earlier today, with or without my other creative workaround.)
Reproducible: Always
Steps to Reproduce:
Visit page at noted URL
Actual Results: Page is displayed truncated
Expected Results: Displayed the entire page
Comment 1•23 years ago
|
||
I see the with linux build 20020708
tried http 1.0, no pipelining and no keep-alive. nothing helped.
lynx and wget manage to get the full page and Mozilla has no problem displaying
it locally.
marking NEW
==> Http
Assignee: attinasi → darin
Component: Layout → Networking: HTTP
QA Contact: petersen → tever
Comment 3•23 years ago
|
||
Assignee | ||
Comment 4•22 years ago
|
||
sounds like a server bug to me. from the log file, i see that the server sends
a connection: close, which means that it is going to close the socket to
indicate the end of the file. server bug IMO, marking WONTFIX.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
Assignee | ||
Comment 5•22 years ago
|
||
reopening, INVALID is a better resolution.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Assignee | ||
Comment 6•22 years ago
|
||
marking INVALID
Status: REOPENED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → INVALID
VERIFIED: invalid
Status: RESOLVED → VERIFIED
QA Contact: tever → httpqa
You need to log in
before you can comment on or make changes to this bug.
Description
•