Chrome: Basic Auth image requests return 401, but not when called directly

Question

Chrome throws 401 restricted errors for Basic auth'd IMG-urls in the vein of http://user:[email protected]/image, but did not do this before with the same resources and code. When called directly, as in "open in new tab" the images load without a hitch. I'm puzzled. Any ideas?

Answer 1

From Chromium issue:

[email protected] wrote:
This is an intentional change - there are lots of security/compatibility tradeoffs that we have to make when tightening up browser security and in this case the decision was made that the compatibility risk was worth it