Closed Bug 3983 Opened 26 years ago Closed 26 years ago

(crasher) Mishandling of HTTP "301-Permanently Moved" Responses

Categories

(Core :: CSS Parsing and Computation, defect, P3)

Other
FreeBSD
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: dirk.campbell, Assigned: troy)

References

()

Details

Hi, Browse to http://www.his.com/~peter. You will be returned a message reading: Netscape is out of memory. Try quitting some other applications or closing some windows. As you can see from the following HTTP headers the GET request results in a "301-(Site)Permanently Moved" response and redirection: c:\wget - S http://www.his.com/~peter --13:02:54-- http://www.his.com:80/~peter => `~peter' Connecting to www.his.com:80... connected! HTTP request sent, fetching headers... 1 HTTP/1.1 301 Moved Permanently 2 Date: Thu, 18 Mar 1999 21:01:13 GMT 3 Server: Apache/1.3.3 (Unix) 4 Location: http://www.his.com/~peter/ 5 Connection: close 6 Content-Type: text/html 7 Location: http://www.his.com/~peter/ [following] --13:02:54-- http://www.his.com:80/~peter/ => `index.html.48' Connecting to www.his.com:80... connected! HTTP request sent, fetching headers... 1 HTTP/1.1 200 OK 2 Date: Thu, 18 Mar 1999 21:01:14 GMT 3 Server: Apache/1.3.3 (Unix) 4 Connection: close 5 Content-Type: text/html 6 0K -> 13:02:55 (845.70 KB/s) - `index.html.48' saved [866] I have also verified this condition via a packet trace. I'm actually trying to troubleshoot an issue with an ISP's customer. I understand that a response isn't generally returned here, but it would be appreciated. Thanks for your time. Any questions, please ask. Dirk Campbell 408-220-2200
Summary: 4.5 & 4.51 Mishandling of HTTP "301-Permanently Moved" Responses → Mishandling of HTTP "301-Permanently Moved" Responses
[Reproduced using 3.18.99 MacOS & Win32 builds of Seamonkey.]
[...which is why I suggested Dirk to submit it as a Seamonkey bug, even if he's encountering it in 4.5, as well.]
Severity: normal → major
Summary: Mishandling of HTTP "301-Permanently Moved" Responses → (crasher) Mishandling of HTTP "301-Permanently Moved" Responses
[At risk of resembling a Burma Shave advertisement, I also note that this does in fact crash Seamonkey immediately and reproducibly, rather than merely yield the low memory error that Dirk encountered on 4.5 and 4.51.]
Assignee: rickg → gagan
Component: Parser → Networking Library
[And, finally, reassigning to gagan. ;-]
QA Contact: 3847 → 3819
Assignee: gagan → peterl
Component: Networking Library → Style System
It doesn't seem to indicate any problem with the 301 response. The "crash" is an assertion failure from the nsCSSFramConstructor. So assigning to "style system" owner...
Assignee: peterl → troy
This crashes in CantRenderReplacedElement. Over to you troy...
This may or may not be pertinent .... FYI - in addition to experiencing this phenomenon with 4.5 and 4.51 on an NT workstation, I also note an identical occurrence using RedHat Linux 5.2 with Netscape 4.5. Thx.
This may or may not be pertinent .... FYI - in addition to experiencing this phenomenon with 4.5 and 4.51 on an NT workstation, I also note an identical occurrence using RedHat Linux 5.2 with Netscape 4.5. Thx.
Just so it's clear, it's hitting an assert. The assert is there so we catch the function being used in a way that wasn't intented...
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Changed CantRenderReplacedElement() to handle APPLET tag as well
Status: RESOLVED → VERIFIED
Marking verified, I don't see this crashing on 3/25 Linux builds. Dirk, please speak up if you're still seeing it. Thanks.
You need to log in before you can comment on or make changes to this bug.