UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/601.5.17 (KHTML, like Gecko) Version/9.1 Safari/601.5.17

Steps to reproduce the problem:
1. Go to http://staging-passbook.greenapes.net/create/reward/850137292659715881?staging
2. Chrome downloads the file
3. Open the file

What is the expected behavior?
Chrome should automatically open .pkpass files, like Safari does. They are Apple Wallet files, and the default file handler of the operating system shows a top-level window asking the user to add it to the iCloud Wallet (and thus synchronize with the iPhone).

If you try the same link on Safari, you can see the expected behavior.

What went wrong?
Chrome downloaded the file instead of opening it. This is an unexpected results for users, as Wallet cards are not exposed as "files" in most (all?) user interface paths on iOS and OSX. Users are not even aware they are "files" behind the scenes, they usually just click on links (or buttons) and get shown the Apple Wallet screen to confirm adding them.

In fact, Safari doesn't even add the file to the Downloads folder, as users are not supposed to manage them manually. It is probably downloaded in a temporary directory and opened from there.

Did this work before? Yes Chrome 23

Chrome version: 49.0.2623.110  Channel: stable
OS Version: OS X 10.11.4
Flash Version: 

I searched the tracker to see if the behavior was disabled after Chrome 23 because of security concerns. I can't think of any, but obviously you know better.

The expected Content-Type for Apple Wallet files is application/vnd.apple.pkpass. Safari on iOS doesn't open the files if they're not being served with this specific Content-Type.

The issue was already reported ( issue #344851 ) but was automatically closed after a year of non interaction.