It may not be a bug, but I've seen this with mozilla .6 and Netscape 6 and the old netscape under linux on this one page (URL above). Netscape 4.75 for windows used to just ignore it, so maybe if you could tell me what's causing it, we can get either the browser or the HTML on the page fixed. Go to the page with mozilla 0.6. There are three ads arranged horizontally, except it wont display the one on the left, just a dialog box that says "application octet-stream can not be displayed," then save or open. It also has a check box which is checked, but greyed out. If I could uncheck the box it would probably stop irritating me, so that's a bug in the browser as far as I'm concerned. On the other hand, if you could just tell me what about that little ad on the left is causing it, I'll get Chet to fix that, though you'll still have the greyed checkbox problem to deal with. Thanks Jason Powers
The iframe in question has src="http://www.portalofevil.com/banners/3/content120x60.x" Trying to get the URL by hand: ~% telnet www.portalofevil.com 80 Trying 22.214.171.124... Connected to www.portalofevil.com (126.96.36.199). Escape character is '^]'. GET /banners/3/content120x60.x HTTP/1.0 HTTP/1.1 200 OK Server: Microsoft-IIS/4.0 Date: Mon, 18 Dec 2000 20:05:34 GMT Content-Type: application/octet-stream Accept-Ranges: bytes Last-Modified: Thu, 07 Dec 2000 14:43:56 GMT ETag: "544860205c60c01:70a0" Content-Length: 1642 So www.portalofevil.com needs to fix their broken web server (or maybe broken CGI) to return content-type: text/html Mozilla is doing exactly what it should be given those headers from the server. So as a Mozilla bug this is probably INVALID.
ie5 gets this right, we fail (maybe correctly so) but I'll let the folks in Networking make that call.
Assignee: asa → neeti
Status: UNCONFIRMED → NEW
Component: Browser-General → Networking
Ever confirmed: true
QA Contact: doronr → tever
This bug should probably be marked "invalid." See bug 68421.
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.