Incorrect Content-Type results in firmware files opening in the browser

[0nelight]

Download-Links to a notable amount of built Images via the Browser-Interface of the public Firmware-Selector-Server on the public ASU are being advertised as content-type: text/stream; charset=utf-8 instead of from content-type: application/octet-stream the Webserver running on ASU.

This leads to the Issue where, when clicking on the Download-Button, instead of Firefox opening the Download-File-Dialog, it interprets the File as a Webpage and tries to render it. Workaround is clicking "Save Target as".

I am not sure if I should put this here or at ASU - therefore I created a Ticket there too.

While Chrome Browser seems to take care of this misconfiguration, Firefox doesn't.

[mwarning]

I cannot reproduce the problem. With Firefox 131.0.3 the generated images are downloaded as octet-stream.

[0nelight]

Hmm.. strange - for what device you produced your image? You applied a custom config?

On my place here I tried with raspi3 device and set rootpw and ip and I get as content-type: text/stream; charset=utf-8 in firefox and in chrome. Chrome then does some stuff to get this right anyway, Firefox takes "text" as "text". When I download with "save file as" the image works flawlessly.

Also tried in a private window with all firefox and chrome extensions disabled - still content-type "text".

[0nelight]

For "8devices Lima" you are right.. there the Type is correct octet-stream:

But for "Raspberry Pi 3B" it is not:

I suspect the "gz" compression is the reason. Maybe related to this Issue?

[AliveDevil]

Moved to appropriate ticket openwrt/asu#1059.

[mwarning]

Thank you for figuring this out. Let me close this ticket and hope this will get fixed on the ASU side.