Downloading resources on Android devices returns unknown file in Google Chrome, or internal browser but not in Firefox for Android!

Short version

  • Do not rely on self signed certificate for android when downloading resources: android download manager wont work (below Android 4.1.4 SSL was even not supported in download manager)
  • Android do not support all kind of SSL Cipher, check the compatibility table below

Long Story

On some Android devices clicking the download link return back an error and show an 'Unknown file'. The file of an initial size of 790kb get partially and randomly downloaded: sometimes you get 140kb, sometimes 224kb or more.

There is a workaround: if one lets the cursor on the link and clicks 'Save' then the saved document is correct and can be opened.

This issue appear on some Android phone, not on Android tablet (???) and never on iOS (sic)

Looking  at the logs, we have found that In Apache access log the resource-size returned is not the same as in Tomcat access log (only when client is Android). Using Desktop class browser (Google Chrome, Firefox, Opera, Safari) the sizes returned by Tomcat and Apache is the same!

After  a lot of try and error we found out that Android is able to download properly the resource when connecting directly to tomcat (e.g. without SSL), however in this case there is a VERY strange behaviour:

So, when we try to download the resource via HTTP, android needs to connect twice! The first connection seems to abort and only the second connection (Android download manager) is able to fetch everything. 

After that, we enabled the debug logging in Apache and had look at the output.

[Tue Jan 26 16:06:29 2016] [info] Initial (No.1) HTTPS request received for child 0 (server skye3.innoveo.com:443)
[Tue Jan 26 16:06:29 2016] [debug] mod_proxy_http.c(56): proxy: HTTP: canonicalising URL //localhost:8443/xx.pdf
[Tue Jan 26 16:06:29 2016] [debug] proxy_util.c(1525): [client 172.16.2.176] proxy: http: found worker http://localhost:8443/ for http://localhost:8443/xx.pdf
[Tue Jan 26 16:06:29 2016] [debug] mod_proxy.c(1026): Running scheme http handler (attempt 0) [Tue Jan 26 16:06:29 2016] [debug] mod_proxy_http.c(1982): proxy: HTTP: serving URL http://localhost:8443/xx.pdf [Tue Jan 26 16:06:29 2016] [debug] proxy_util.c(2102): proxy: HTTP: has acquired connection for (localhost) [Tue Jan 26 16:06:29 2016] [debug] proxy_util.c(2158): proxy: connecting http://localhost:8443/xx.pdf to localhost:8443 [Tue Jan 26 16:06:29 2016] [debug] proxy_util.c(2285): proxy: connected /xxxxx.pdf to localhost:8443 [Tue Jan 26 16:06:29 2016] [debug] mod_proxy_http.c(1741): proxy: start body send [Tue Jan 26 16:06:29 2016] [info] [client 172.16.2.176] (104)Connection reset by peer: core_output_filter: writing data to the network [Tue Jan 26 16:06:29 2016] [info] [client 172.16.2.176] (103)Software caused connection abort: SSL output filter write failed. [Tue Jan 26 16:06:29 2016] [debug] mod_proxy_http.c(1851): proxy: end body send [Tue Jan 26 16:06:29 2016] [debug] proxy_util.c(2120): proxy: HTTP: has released connection for (localhost) [Tue Jan 26 16:06:29 2016] [info] [client 172.16.2.176] Connection to child 3 established (server skye3.innoveo.com:443) ... ~removed useless debug output~ [Tue Jan 26 16:06:29 2016] [debug] ssl_engine_kernel.c(1966): [client 172.16.2.176] SSL virtual host for servername skye3.innoveo.com found [Tue Jan 26 16:06:29 2016] [debug] ssl_engine_kernel.c(1853): OpenSSL: Loop: SSLv3 read client hello A [Tue Jan 26 16:06:29 2016] [debug] ssl_engine_kernel.c(1853): OpenSSL: Loop: SSLv3 write server hello A [Tue Jan 26 16:06:29 2016] [debug] ssl_engine_kernel.c(1853): OpenSSL: Loop: SSLv3 write certificate A [Tue Jan 26 16:06:29 2016] [debug] ssl_engine_kernel.c(1853): OpenSSL: Loop: SSLv3 write key exchange A [Tue Jan 26 16:06:29 2016] [debug] ssl_engine_kernel.c(1853): OpenSSL: Loop: SSLv3 write server done A [Tue Jan 26 16:06:29 2016] [debug] ssl_engine_kernel.c(1853): OpenSSL: Loop: SSLv3 flush data Tue Jan 26 16:06:29 2016] [debug] ssl_engine_io.c(1929): OpenSSL: read 5/5 bytes from BIO7f1a4c1230d0 [mem: 7f1a4c17a493] (BIO dump follows) ... ~removed useless debug output~ [Tue Jan 26 16:06:29 2016] [debug] ssl_engine_kernel.c(1853): OpenSSL: Loop: SSLv3 read client key exchange A [Tue Jan 26 16:06:29 2016] [debug] ssl_engine_io.c(1929): OpenSSL: read 5/5 bytes from BIO7f1a4c1230d0 [mem: 7f1a4c17a493] (BIO dump follows) ... ~removed useless debug output~ [Tue Jan 26 16:06:29 2016] [debug] ssl_engine_kernel.c(1853): OpenSSL: Loop: SSLv3 read finished A [Tue Jan 26 16:06:29 2016] [debug] ssl_engine_kernel.c(1853): OpenSSL: Loop: SSLv3 write session ticket A [Tue Jan 26 16:06:29 2016] [debug] ssl_engine_kernel.c(1853): OpenSSL: Loop: SSLv3 write change cipher spec A [Tue Jan 26 16:06:29 2016] [debug] ssl_engine_kernel.c(1853): OpenSSL: Loop: SSLv3 write finished A [Tue Jan 26 16:06:29 2016] [debug] ssl_engine_kernel.c(1853): OpenSSL: Loop: SSLv3 flush data [Tue Jan 26 16:06:29 2016] [debug] ssl_engine_kernel.c(1849): OpenSSL: Handshake: done [Tue Jan 26 16:06:29 2016] [info] Connection: Client IP: 172.16.2.176, Protocol: TLSv1.2, Cipher: ECDHE-RSA-AES256-SHA (256/256 bits) [Tue Jan 26 16:06:29 2016] [info] [client 172.16.2.176] (70014)End of file found: SSL input filter read failed. [Tue Jan 26 16:06:29 2016] [info] [client 172.16.2.176] Connection closed to child 2 with standard shutdown (server skye3.innoveo.com:443) [Tue Jan 26 16:06:29 2016] [info] [client 172.16.2.176] Connection to child 0 established (server skye3.innoveo.com:443) ...

So we see, the intial SSL connect works, we can see the request issued and the proxy request. Body is written and then "connection reset by peer"

After careful search it is pretty sure that we are running into this problem: https://code.google.com/p/chromium/issues/detail?id=440951
Summary: 
when you try to download stuff with chromium it works (even from unsecure sources), this is why the first connect is okay. however chromium interrupts the download to hand it over to android download manager (this is why actually displaying pictures works, despite the fact that they are delivered though the same pipeline, e.g. skye code, tomcat version, apache and ssl). this is also why we see two downloads per click in the log files. Problem is however that android download manager does NOT NEVER EVER download stuff from unsecure sources (e.g. selfsigned certs) and thus the final download fails. this is also true for the default andoid browser, because they also use the android download manager.

Solution: the only solution was be to upgrade to valid SSL  certificates (Verizon, Verisign or any other) instead of self signed. This increase the number of Android device working but unfortunately  some Android devices were still NOT able to download resources with a valid SSL cert...

By using the Android SDK debug console (adb.exe logcat > file.txt) of android, we saw the following:

	Line 7487: D/DownloadManager( 3054): [1] Starting
	Line 7489: W/DownloadManager( 3054): [1] Stop requested with status HTTP_DATA_ERROR: Handshake failed
	Line 7491: D/DownloadManager( 3054): [1] Finished with status WAITING_TO_RETRY

This show again that the initial connect to our server happen correctly but return partial content but is then forwarded to the download manager that try to build another connection that is still fail

Solution: change Apache cipher suite according to the table below.

Android compatibility table

http://developer.android.com/reference/javax/net/ssl/SSLEngine.html

Depending on which version of android you would like to support you'll  have to find a cipher suite that is supported by iOS, Android while not sacrificing too much security. 

Android Version Released API Level Name Build Version Code
Android 6.0 August 2015 23 Marshmallow Android.OS.BuildVersionCodes.Marshmallow
Android 5.1 March 2015 22 Lollipop Android.OS.BuildVersionCodes.LollipopMr1
Android 5.0 November 2014 21 Lollipop Android.OS.BuildVersionCodes.Lollipop
Android 4.4W June 2014 20 Kitkat Watch Android.OS.BuildVersionCodes.KitKatWatch
Android 4.4 October 2013 19 Kitkat Android.OS.BuildVersionCodes.KitKat
Android 4.3 July 2013 18 Jelly Bean Android.OS.BuildVersionCodes.JellyBeanMr2
Android 4.2-4.2.2 November 2012 17 Jelly Bean Android.OS.BuildVersionCodes.JellyBeanMr1
Android 4.1-4.1.1 June 2012 16 Jelly Bean Android.OS.BuildVersionCodes.JellyBean
Android 4.0.3-4.0.4 December 2011 15 Ice Cream Sandwich Android.OS.BuildVersionCodes.IceCreamSandwichMr1
Android 4.0-4.0.2 October 2011 14 Ice Cream Sandwich Android.OS.BuildVersionCodes.IceCreamSandwich
Android 3.2 June 2011 13 Honeycomb Android.OS.BuildVersionCodes.HoneyCombMr2
Android 3.1.x May 2011 12 Honeycomb Android.OS.BuildVersionCodes.HoneyCombMr1
Android 3.0.x February 2011 11 Honeycomb Android.OS.BuildVersionCodes.HoneyComb
Android 2.3.3-2.3.4 February 2011 10 Gingerbread Android.OS.BuildVersionCodes.GingerBreadMr1
Android 2.3-2.3.2 November 2010 9 Gingerbread Android.OS.BuildVersionCodes.GingerBread
Android 2.2.x June 2010 8 Froyo Android.OS.BuildVersionCodes.Froyo
Android 2.1.x January 2010 7 Eclair Android.OS.BuildVersionCodes.EclairMr1
Android 2.0.1 December 2009 6 Eclair Android.OS.BuildVersionCodes.Eclair01
Android 2.0 November 2009 5 Eclair Android.OS.BuildVersionCodes.Eclair
Android 1.6 September 2009 4 Donut Android.OS.BuildVersionCodes.Donut
Android 1.5 May 2009 3 Cupcake Android.OS.BuildVersionCodes.Cupcake
Android 1.1 February 2009 2 Base Android.OS.BuildVersionCodes.Base11
Android 1.0 October 2008 1 Base Android.OS.BuildVersionCodes.Base

It is always a good idea to validate your SSL settings by using one the these online services (In no particular order). Some even report if you are vulnerable to some common SSL attacks ()

You might like also

Docker essential tools: Dive to navigate docker image content
If you want to explore the content of a docker image, Dive is THE tool for exploring a docker image, layer contents, and discovering ways to shrink the size of your Docker image. Note that we will be exploring the image not the container: viewing the container and the image are not the same thing. You can get most of the time a bash access to a running container with  docker run -it image_name sh Or following for images with an entrypoint docker …
16 Days ago
#ALPINE-HACK19 4 – 5 October, 2019
On October 4th and 5th, the AlpineHack19 will be held, a blockchain-themed hackathon. The opportunity to bring together software developers, hackers, information technology enthusiasts and SMEs to showcase their know-how. The aim for the participants is to develop a functioning open-source software or #hardware prototype – solutions that eliminate real problems, for real companies. #Blockchain Technology will be the center of all predefined challenges. 24 hours of #Innovation, personal development and lots of fun. I will be there as hackathon mentor …
125 Days ago
CryptoMountain Rocks in Sion 3-5 october 2019
CryptoMountain Rocks is a platform for Blockchainers from the Crypto Valley and beyond that offers a very inter-active conference with presentations, panels and talks battles. I will be there 3 days as a speaker and hackathon mentor. The event discusses latest Blockchain applications and talks about the impact of the new token economy on the way we do business. In parallel there will be the first CryptoMountain Rocks #ALPINE-HACK19 covering themes such as Agriculture, Energy and Supply Chain. …
125 Days ago
A git workflow that is easy and scale for product development
There are numerous GIT workflow floating around like Centralized Workflow, Gitflow, Forking flow and Feature Branch Workflow Over the last 10 years, I have followed this really simple workflow, similar to the forking flow. it allow Parallel Development, features branches can be merged to any release branches or ideally Master Collaboration Feature branches also make it easier for two or more developers to collaborate on the same feature We consider Master the stable version of the product, this branch should be deployed automatically using …
149 Days ago
Using free Cloudflare for CDN and DDoS protection
Cloudflare, Inc. is an American web infrastructure and website security company, providing content delivery network services, DDoS mitigation, Internet security, and distributed domain name server services.  It will cost you 0$ (DDOS, CDN) to 20$ or more and offer you the following advantages DDoS is short for Distributed Denial of Service. DDoSis a type of DOS attack where multiple compromised systems, which are often infected with a Trojan, are used to target a single system causing a Denial of Service …
149 Days ago
Add Docker container logs in Splunk
With Splunk You will be able to optimize container usage by monitoring CPU, memory, disk and network performance metrics from your containers. Pay only for what you need by managing resources and measuring the impact on service reliability and container resource requirements. Get a complete overview of Kubernetes and OpenShift Environments Correlate performance metrics, container logs and OpenShift/Kubernetes configuration and metadata for a better understanding of how your infrastructure is performing and how hosted applications are behaving. …
149 Days ago
Installing latest Splunk in 5 minutes using Docker
From 0 to Splunk in 5 minutes using Docker and Compose Splunk is an American multinational corporation headquartered in San Francisco, California, which produces software for searching, monitoring, and analyzing machine-generated big data, via a web-style interface. Docker is an open source software platform to create, deploy and manage virtualized application containers on a common operating system (OS), with an ecosystem of allied tools.  Compose is a tool for defining and running multi-container Docker applications. With Compose, you use a YAML file to configure your application's services. Then, with …
149 Days ago
Explore 142 Initial Exchange Offering  (IEO) by category, year and country
IEO is currently the most popular fundraising trend in the crypto industry. As the name suggests, Initial Exchange Offering is conducted over the crypto trading platform and exchanges. So unlike ICOs wherein crypto projects directly approach investors, IEOs involve a third-party in the form of crypto exchanges. …
243 Days ago
Security Token Offering (STO) statistics
Security token offering (STO) is a type of fundraising that is performed with a company offering tokenized securities. The defining feature of security token offerings is in its definition. Stocks, bonds and managed property trusts are another examples of securities. …
244 Days ago
systematization of knowledge within major blockchain protocols or consensus
Alexis Gauba presented a systematization of knowledge within major blockchain protocols or consensus, addresses the common challenges …
322 Days ago