file download should be .MP3

Hello,

This is super low priority and I am not able to reproduce this error. I tested on windows10 & android cell phone and it works as expected.

I have a page here: https://ironfeather.com/index.php?page=news&type=view&id=377&select=17

Featuring a MP3 file people can download or stream and for me all work great for me as expected and about 80 other people on various devices all reports works good but one user just contacted me and said the file download as a .BIN extension.

He is using a cellphone (Samsung Galaxy A30)

He renamed the file to MP3 and everything works he says.

I would think this situation is super rare but wanted to report it in case anyone else has the same issue

cheers

stevyn

 

Find out what browser exactly he's using on the device please. E.g. inbuilt Android Browser, some Samsung thing, Chrome, …?

I don't get this TBH, and am questioning whether it's maybe a link elsewhere. Maybe get a screenshot of before they click they link and confirm the exact hyperlink clicked.

HTTP headers:
The URL is to the PHP script, and while it is a .bin file under-the-hood, the URL to that file shouldn't even be exposed because it pipes through the PHP script.

Hi Chris, bit more info.

I posted the link :  https://ironfeather.com/index.php?page=news&type=view&id=377&select=17

on facebook in a firefly tv show discussion group and invited readers to go to my link for the mp3

he replied to me that he was using the   "Facebook Mobile Browser"   on his cellphone, the Samsung Galaxy A30.

So I am not sure exactly what the FB mobile browser is as I dont use it so unsure how it could extract it as a BIN.

Stevyn

At first I thought it was using .bin because Composr is using .bin for the on-disk filenames.

However I think it is an old Android bug whereby it uses .bin when it is not parsing the Content-Type header properly.
http://www.digiblog.de/2011/04/android-and-the-download-file-headers/

We have a semicolon on the end of the content-type header that should not really be there, but isn't really a problem except here.

The linked topic talks about Android 4, which is very old – but my guess is the issue is replicated in Facebook's inbuilt browser, probably based on the original Android Browser.

I'll post a hotfix based on this theory. I don't want to go test this as it would take me a while to try and reproduce.

Automated fix message

TQ said

Hi Folks,

Since the 10.0.44 update, if a user requests the base URL

Code

the page presented is a blank white page.

The inspector reports: Error: An unexpected error occurred, and that's it!

If you access any other other page first then navigate to the home page, all is fine (because it uses the URL below).

If you add: /index.php?page=start to the URL, again, all is fine.

I tried the 10.0.45 update which didn't resolve the problem.

Does anyone have a quick fix for this, I'm loosing all of my traffic?

TQ
 

This issue has now been filed on the tracker as issue #4629, with a fix.