Closed Bug 163424 Opened 23 years ago Closed 23 years ago

.xml postfixed to file names being downloaded - profile related

Categories

(SeaMonkey :: General, defect)

x86
Windows NT
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 120327

People

(Reporter: coffeebreaks, Assigned: Matti)

References

()

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1) Gecko/20020811 Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1) Gecko/20020811 When I try to download the JDK 1.4.1beta from Sun's web site, Mozilla adds a '.xml' extension to the file name. Reproducible: Always Steps to Reproduce: 1. Go to the above mentioned URL (http://java.sun.com/j2se/1.4.1/download.html) 2. Click to download the SDK for Windows (all languages) 3. Click accept on the term and conditions. You are then presented a page that allows you to initiate the download of the JRE. 4. click on the link (do not do Save As as this does NOT reproduces the problem) The link looks like: http://dlres.java.sun.com/JSCDL/download/<big number>/<other big number>/j2sdk-1_4_1-beta-windows-i586.exe Actual Results: File manager opens and offers you to save file as j2sdk-1_4_1-beta-windows-i586.exe.xml Expected Results: File manager opens and offers you to save file as j2sdk-1_4_1-beta-windows-i586.exe I tried to find a dupe usign 'xml download', but couldn't.
Corrected title. I forgot to add that this seems to be a regression.
Summary: .xml prefixed to file names being downloaded → .xml postfixed to file names being downloaded
Sorry to say, it works for me ! Using Trunk build 2002081804 - WinXP. Reporter, it seems that there is younger "release candidate" for 1.1 (dated 18 august). Can you download it and try to see if the bug is still present ? Thanks.
I would really like to download it, but we are on a modem line and it takes quite a long time for me to do so. I will give it a try.
Downloaded latest as pointed on mozillazine.org (http://komodo.mozilla.org/pub/mozilla/nightly/latest-1.1/) Problem still present... Mozilla 1.1 Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1) Gecko/20020818 Note: I downloaded the talkback enabled build (mozilla-win32-talkback.zip).
I've tested opening a new profile: the bug doesn't appear. So the bug is profile related. If there's anything I can do to help, just tell me which part of the profile I may be involved.
Summary: .xml postfixed to file names being downloaded → .xml postfixed to file names being downloaded - profile related
Well, I don't know which part of the profile should be guilty for this bug. Make a backup copy of your guilty profile, and try removing mimetypes.rdf ? It is a possibility :-) But I am not sure this is the right one ! I am not a professionnal in profile handling, but it may be simpler to recreate all your accounts, quit mozilla, and copy your bookmarks (bookmarks.html) and you mail data to your new account. And after, using profile manager, removing the old buggy one. Well, ask for some more help. I hope I helped you a little :-)
WFM 2002081808/winXP Here's what I get: -------------------------------------------------------------------- HTTP/1.1 302 Moved Temporarily Server: Netscape-Enterprise/4.1 Date: Mon, 19 Aug 2002 16:10:56 GMT Content-type: text/plain Location: http://sunsdlc1-1.sjc-colo.bbnplanet.com/servlet/EComFileServlet//ESD2/JSCDL/downloads/j2sdk/1.4.1/978Beta098sdfnv/j2sdk-1_4_1-beta-windows-i586.exe?ActionId=verify&TicketId=DlxZ%2FkuCV1E%3D&TicketServerUrl=zXfAgJjyQd1SQ13APdzMgsQtx4XM8w3WUx5y4FDy4Q%3D%3D Content-length: 0 Connection: close -------------------------------------------------------------------- The other URL doesn't support HEAD, but properly executes GET.
Attached file my mimeTypes.rdf
Seems like my mimeTypes.rtdf contains a strange entry for application/octect-stream. <RDF:Description about="urn:mimetype:application/octet-stream" NC:value="application/octet-stream" NC:description="Extensible Markup Language" NC:fileExtensions="xml" NC:editable="true"> <NC:handlerProp resource="urn:mimetype:handler:application/octet-stream"/> </RDF:Description> Is there a way to look at a log file and see what went wrong?
What went wrong when? Given that entry, this is yet another incarnation of bug 120327....
Well, looks like it. I hesitate a little, but I will follow your comment. Marking this one as dup of 120327 ! *** This bug has been marked as a duplicate of 120327 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: