Bug #9774

#9770 (re-visited) .flatpak file downloads not working

Added by Jordi Guri 5 months ago. Updated 5 months ago.

Status:Closed Start date:03/04/2022
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:-
Chirp Version:daily Platform:Linux
Model affected:flatpak

Description

Hi again, Jim.

Oops, sorry problem #9770 is not quite fixed yet! :)

From your last response in #9770:
+++

That a browser behavioral issue, not a CHIRP website problem.

After extensive reading up on Mime types, Content-Type, http servers & browsers, this bug is not a browser problem.

1. The Mime "Content-Type" for each file (like the Chirp Download files) should be set in the server and not left up to the browser to determine (or change) what the server had intended. Otherwise each browser will have to guess at (or override) what the server's intentions are. For Chirp downloads, in the case of the Chrome browser this assumes that ".flatpak" is a text file, while the Firefox browser assumes that a ".flatpak" is to be downloaded.

2. If you right-click in any browser and select "inspect", and in the "inspect" frame, select "Network", you can then see what the http server's response is for each file request, by selecting each file element on the downloads page.

This is what I am seeing on the https://trac.chirp.danplanet.com/chirp_daily/LATEST/ page for the downloadable files:

filetype: .flatpak
------------------
Accept-Ranges: bytes
Content-Length: 19262872 <--- Content-Type is NOT specified by the server
Date: Fri, 04 Mar 2022 20:16:58 GMT
ETag: "220aad-125ed98-5d85a71d34a43"
Last-Modified: Sat, 19 Feb 2022 08:04:11 GMT
Server: Apache/2.2.22 (Ubuntu)
X-Content-Type-Options: nosniff
X-Frame-Options: sameorigin

filetype: .gzip
----------------
Accept-Ranges: bytes
Content-Length: 1037302
Content-Type: application/x-gzip <--- Content-Type is specified by the server
Date: Fri, 04 Mar 2022 20:52:16 GMT
ETag: "220aac-fd3f6-5d85a719343d1"
Last-Modified: Sat, 19 Feb 2022 08:04:07 GMT
Server: Apache/2.2.22 (Ubuntu)
X-Content-Type-Options: nosniff
X-Frame-Options: sameorigin

filetype: .exe
---------------
Accept-Ranges: bytes
Content-Length: 11304216
Content-Type: application/x-msdos-program <--- Content type is specified by the server
Date: Fri, 04 Mar 2022 20:56:25 GMT
ETag: "220aaa-ac7d18-5d85a7161f2f5"
Last-Modified: Sat, 19 Feb 2022 08:04:04 GMT
Server: Apache/2.2.22 (Ubuntu)
X-Content-Type-Options: nosniff
X-Frame-Options: sameorigin

In summary, there is no Mime "Content-Type" specified for ".flatpak" files in the Apache server for chirp.danplanet.com. Thus, different browsers will make different assumptions for these files coming from Chirp's Apache server. For filetype ".flatpak" the "Content_Type" needs to be set in the Chirp Apache server (.htaccess file?).

I found further reading on this at: https://developer.mozilla.org/en-US/docs/Learn/Server-side/Configuring_server_MIME_types

For your info ...

Jordi

History

Updated by Jim Unroe 5 months ago

  • Status changed from New to Feedback

Still not a CHIRP bug. You would be better of mentioning this in the [chirp_devel] mailing list where a website manager will see it.

Jim KC9HI

Updated by Jordi Guri 5 months ago

Sorry Jim. I got the wrong forum. Will do thanks.

Jordi

Updated by Bernhard Hailer 5 months ago

  • Status changed from Feedback to Closed
  • Model affected changed from (All models) to flka
  • Platform changed from Windows to Linux

Updated by Bernhard Hailer 5 months ago

  • Model affected changed from flka to flatpak

Also available in: Atom PDF