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?

Arcanum

I've encountered the same. I guess it has something to do with the latest chrome update. In Firefox everything works as exspected. – Rheology

Experiencing the same issue with Chrome v30. – Nikolia

After further research the issue has been raised with the Chromium team - code.google.com/p/chromium/issues/detail?id=303046 – Nikolia

If the image is hosted on a different domain from the webpage, and you try to do "Copy URL" it copies: "http://<webpage_domain/user:[email protected]/image" – Columniation

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

Lamellirostral