Firebird problems
I'm having a slight issue with Firebird.
Many times, when I open a .torrent link, it shows a whole bunch of gibberish. I have to right click, save target as, then find it and open it.
Is there something I can do to fix this, so that it will download the .torrent file just by clicking the link rather than showing me a bunch of gibberish?
It does this for various .avi .mov etc files posted here, too.
Registered User
Posts: 676
(3/13/04 9:22 am) Reply
Re: Firebird problems
That happens to me on certain webpages, usually when they try and conceal the torrent's link through some PHP popup script.
Does it happen on every torrent you choose, or just ones from a certain webpage?
---------- "You there, fill it up with petroleum distillate, and re-vulcanize my tires, post-haste! Also, I'd like to send this letter to the Prussian consulate in Siam by aeromail. Am I too late for the 4:30 autogyro?" - Monty Burns
deuce Registered User
Posts: 1026
(3/13/04 9:52 am) Reply
Re: Firebird problems
Yeah upgrade to firefox the newer version, it resolves the problem
Re: Firebird problems
I've been reinstalling it a lot lately. ABC's been screwed up lately. I would advise anyone against upgrading past 2.5, by the way. At least until the chaos dies down.
InvisiBill Registered User
Posts: 349
(3/14/04 7:42 pm) Reply
Re: Firebird problems
Besides BT client problems, it could be an issue with the server hosting the file. According to the RFCs, the browser must use the MIME type specified by the server. If the server says a file is plaintext, the browser has to show it as plaintext.
All recent versions of IE, as far as I know, don't do this. IE "sniffs" the file and tries to figure out what type of file it is. Many people who don't know what they're doing are setting up webservers now. They're not setting the server up for new filetypes, so the server is telling the browser that it's plaintext. This is nice when MoronJoe can't configure his web server properly, and it says that cool.wmv is a plaintext file - IE figures out that it's actually a movie file. However, IE also says that sourcecode.txt on my site is a webpage, because it has HTML tags in it.
Mozilla added a check to the code about two months ago. If the server says a file is plaintext, but there are binary characters in the file, it ignores what the server says. Note that Mozilla doesn't "sniff" like IE does, it just handles one impossible case - the server says it's text, but the file contains non-text.
Mozilla's method will give you problems on sites that aren't configured correctly. IE's method will give you problems with files that contain data that "they shouldn't" - like my text file containing HTML tags. The problems encountered with Mozilla would go away if people set up their servers properly. IE's method can never work 100%, unless they add code to email the author and ask how they want the page to be handled (which is basically the point behind forcing browsers to use MIME types anyway) or everyone on the internet names every file to Windows standards and never includes data of one type (HTML tags) in a file of another type (plaintext file).
Anyway, Mozilla just does one simple check for bad MIME types (nontext in a plaintext MIME type). Depending on how the server is set up, it could be sending the file as plaintext in a way that Mozilla's check isn't catching it.