# Nginx Load Balancer - Random file named "download" when using Chrome

**URL:** <https://www.ruby-forum.com/t/nginx-load-balancer-random-file-named-download-when-using-chrome/243749>\
**Category:** NGINX\
**Created:** [December 30, 2015, 5:24am UTC](https://www.ruby-forum.com/t/nginx-load-balancer-random-file-named-download-when-using-chrome/243749 "2015-12-30T05:24:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rafa\_F](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/958977/32.png) [@Rafa\_F](https://www.ruby-forum.com/u/Rafa_F)\
**Post date:** [December 30, 2015, 5:24am UTC](https://www.ruby-forum.com/t/nginx-load-balancer-random-file-named-download-when-using-chrome/243749/1 "2015-12-30T05:24:35Z")

</div>

Hi guys,

We are using Nginx 1.4.6 as a Load Balancer for our website. Sometimes,  
when a user loads the website, the browser will start downloading a  
file named “download” which contains the HTTP Response headers. So far,  
what we know is that it only happens when the browser is Chrome and it’s  
maybe once every 60-70 page loads. I’ve narrowed it down to the LB since  
loading the page directly on the app server never triggers a download.

You also see the following error : “Resource interpreted as Document but  
transferred with MIME type application/octet-stream:” in the Chrome  
console.

Any ideas?

---

<div class="post-metadata">

**Author:** ![nuxwin](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/53a042/32.png) [@nuxwin](https://www.ruby-forum.com/u/nuxwin)\
**Post date:** [December 30, 2015, 11:53am UTC](https://www.ruby-forum.com/t/nginx-load-balancer-random-file-named-download-when-using-chrome/243749/2 "2015-12-30T11:53:39Z")

</div>

nginx serves content, but does not generate it.  
If users download anything, it is either related to the application or  
to  
the client (browser module?).

I suggest you check both sides to find where/how this URI is generated  
and  
why it is accessed.  
The incorrect MIME type means a backend has badly positioned a  
Content-Type  
header, or in its absence nginx has been configured to serve this URI as  
application/octet-stream (cf.  
[Module ngx\_http\_core\_module](http://nginx.org/en/docs/http/ngx_http_core_module.html#default_type)).  
For its content, as stated before, nginx does not generate it by itself:  
you will need to find its source.

## ​Happy debugging,​

_B. R._

On Wed, Dec 30, 2015 at 5:23 AM, Laurent D. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)