UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36

Steps to reproduce the problem:
1. Set up a page which sets a HPKP header which sets the header name twice (aka starts with "Public-Key-Pins: Public-Key-Pins: pin-sha256..."), the pin that is valid for the current page should not be the first.
2. load page
3. check chrome://net-internals/#hsts for HPKP
4. Chrome accepted the HPKP header, however it ignored the first pin that was set.

What is the expected behavior?
Given the "shoot in the foot" potential of HPKP all invalid HPKP headers should probably be ignored.

What went wrong?
Chrome accepted the header, but ignored one of the pins. That seems dangerous and increases the risk that website owners configure their site in a way that makes it unaccessible.

Did this work before? N/A 

Chrome version: 53.0.2785.143  Channel: n/a
OS Version: 
Flash Version: 

I tested this in firefox and it behaves as expected: It ignores the header and shows an error in the developer console.

I have set up a test page:
https://dhpkp.tlsfun.de/

The test can be replicated by using an apache and set a pin like this:
header set Public-Key-Pins "Public-Key-Pins: pin-sha256=\"ZR7UrkdiJKbmmLXiQlwxmS129Oy9OjzjfOIkMUiK5ZQ=\";pin-sha256=\"YLh1dUR9y6Kja30RrAn7JKnbQG/uEtLMkBgFF2Fuihg=\";pin-sha256=\"sRHdihwgkaib1P1gxX8HFszlD+7/gTfNvuAybgLPNis=\";pin-sha256=\"nB+CrX0Lzjgq1mfXWxlcqKnzVxh2M+YhNtJN87NaZXc=\"; max-age=604800;"