Closed Bug 12936 Opened 25 years ago Closed 25 years ago

Invalid File Type in several places.

Categories

(Core :: Networking, defect, P3)

x86
Windows 98
defect

Tracking

()

VERIFIED DUPLICATE of bug 17647

People

(Reporter: jer, Assigned: jud)

References

()

Details

M9 on Win 98, this is. Steps to reproduce: 1. Attempt to go to any valid http://members.xoom.com/USERNAME/ page. Results: Unknown File Type window will pop up, most likely due to xoom's advertising frame at the top of the browser window. Console Window has: DocLoaderFactory: Unable to create ContentViewer for command=view, content-type=(null) Document: Done (0.99 secs) Document http://members.xoom.com/don/ loaded successfully JavaScript error: window.arguments has no properties URL: file:///C|/MOZILLA/M9/BIN/chrome/global/content/default/unknownContent.xul LineNo: 24 Expected results: Successful load of page. Comments: This affects all member pages at xoom.com. Is it related to apprunner's inability to query bugzilla?
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
This isn't an issue in newer builds (1999090408) so I'm marking it worksforme.
*** Bug 13157 has been marked as a duplicate of this bug. ***
Status: RESOLVED → REOPENED
Apparently I'm an idiot. I went to the URL in 4.5, rather than in Mozilla. See bug 13157 for the current error. It displays a blank page, but the console window says the page loaded successfully.
Resolution: WORKSFORME → ---
Clearing WORKSFORME resolution due to reopen of this bug.
Assignee: don → leger
Status: REOPENED → NEW
Summary: Invalid FIle Type in several places. → Invalid File Type in several places.
Status: NEW → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → DUPLICATE
If bug 13157 describes the current problems, then isn't this bug a duplicate of bug 13157? Marking as such. Please reopen if I'm wrong. *** This bug has been marked as a duplicate of 13157 ***
I think that this bug was being blocked by 13157. Hard to say whether it is that, or just a different end result from the same problem.
Status: RESOLVED → REOPENED
Depends on: 13157
Now that 13157 is fixed, this has reemerged.
Resolution: DUPLICATE → ---
Assignee: leger → gagan
Status: REOPENED → NEW
Component: Browser-General → Necko
QA Contact: leger → tever
May be a dup...setting QA contact and component to find out.
Bulk move of all Necko (to be deleted component) bugs to new Networking component.
Status: NEW → ASSIGNED
Smells like URL dispatching issues. CC'ing mscott since I don't have the update on that as yet...
Assignee: gagan → valeski
Status: ASSIGNED → NEW
Target Milestone: M14
Doesn't sound like url dispatching to me. Sounds like we're getting a bad content type for some reason. -> Jud
Status: NEW → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → DUPLICATE
The problem was that the server was (it's not anymore) sending "(null)" as the content type for something. If the server starts sending it again, we'll be ok per my fix to 17647. *** This bug has been marked as a duplicate of 17647 ***
Status: RESOLVED → VERIFIED
verified duplicate of 17647.
You need to log in before you can comment on or make changes to this bug.