Re: Issue 91814 in chromium: Iframe Basic Authentication Issue

[chro...@googlecode.com]

Updates:
Status: Assigned
Owner: tse...@chromium.org
Cc: cev...@chromium.org
Labels: -Area-Undefined Area-Internals Internals-Network-Auth

Comment #1 on issue 91814 by cbent...@google.com: Iframe Basic
Authentication Issue
http://code.google.com/p/chromium/issues/detail?id=91814

tsepez: In this case, the iframe'd content does HTTP auth and is from a
different origin than the top-level page.

[chro...@googlecode.com]

Comment #4 on issue 91814 by dph1...@gmail.com: Iframe Basic Authentication
Issue
http://code.google.com/p/chromium/issues/detail?id=91814

Another work around I found is to authenticate directly to that weblink and
then try using the iframe in the webpage, then it works. But this again is
not comfortable for clients, if we have multiple such links in a web
page/site. Rather than starting chrome with this flag, is it possible to
give a check/uncheck preference option for this in the browser preferences?

[chro...@googlecode.com]

Comment #6 on issue 91814 by mrishad...@gmail.com: Iframe Basic
Authentication Issue
http://code.google.com/p/chromium/issues/detail?id=91814

I am facing the same problem, iFrames are auto generated and I cannot ask
my users to start Chrome with some flag.
OR
Is there a way to hard code the authentication details and do not prompt
for the details because once the session is made. it works fine.


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Comment #8 on issue 91814 by tur...@gmail.com: Iframe Basic Authentication
Issue
http://code.google.com/p/chromium/issues/detail?id=91814

This used to happen to me also, but in the latest chrome update (26) i do
get the authentication dialog.
does anyone else notice that? did chrome change the policy specified in
http://blog.chromium.org/2011/06/new-chromium-security-features-june.html
section 13 ?

[chro...@googlecode.com]

Comment #9 on issue 91814 by tur...@gmail.com: Iframe Basic Authentication
Issue
http://code.google.com/p/chromium/issues/detail?id=91814

Yes, chrome did change the behaviour and now they behave like all the other
browsers,
https://code.google.com/p/chromium/issues/detail?id=174179