Closed
Bug 273587
Opened 20 years ago
Closed 19 years ago
No fetching of remote datasources w/ HTTP authentication
Categories
(Core Graveyard :: RDF, defect)
Tracking
(Not tracked)
People
(Reporter: moe, Unassigned)
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041001 Firefox/0.10.1 StumbleUpon/1.998 Build Identifier: Firefox 1.0 This bug seems related to 33206. Fetching of remote RDF datasources is temperemental when HTTP auth is involved. i have a JS func which does GetDataSource and attaches an nsIRDFXMLSink. the other bug (33206) still stands, in that the auth dialog never pops up..the onError of the sink gets called with a NO_INTERFACE error (2147500034). HOWEVER, if the authentication information is encoded in the URL itself, eliminating the need for an authentication dialog to ever appear, things still go a bit pear-shaped. everythings works fine, except in the following scenario: javascript function gets called function calls a second function, which does a GetDataSource, attaches a sink. the second function returns, and the calling function does a GetDataSource on a different data source, and attaches a sink. invariably the datasource in the second function will get loaded fine but the DS in the first does not. so chronologically, the first call to GetDataSource succeeds and the second does not. convoluted, i know. interestingly, the error code passed to the onError of the sink is NO_INTERFACE, the same as with the auth box bug. i have attached the (commented) javascript, as well as the HTTP log. Reproducible: Always Steps to Reproduce: have a xul window call the javascript function callMeFirst(). the URLs in the code have be X'ed out as they are sensitive, and will need to be replaced with a different URL requiring http authentication Actual Results: see the description Expected Results: loaded the datasources
| Reporter | ||
Comment 1•20 years ago
|
||
| Reporter | ||
Comment 2•20 years ago
|
||
Comment 3•20 years ago
|
||
Darin, I'd need some opinions here. I'm not at all sure about the implications of http auth and the caching of RDF DataSources plus their uniqueness. It gives me an awkward feeling that I could keep something that got a window context of some sort (for the auth prompt) around, possibly longer than the window. How bad would that be?
Comment 4•20 years ago
|
||
It could be bad, but only if you have multiple users of the same browser and they wish to be private from eachother. The same-origin checks prevent websites from accessing the RDF datasources of other domains.
| Reporter | ||
Comment 5•20 years ago
|
||
more strangeness: - even with the authentication hardcoded in the URL sometimes an auth prompt comes up?! - additional problems occur when opening the XUL from an browser overlay, i.e. Tools menu.
Comment 6•19 years ago
|
||
*** This bug has been marked as a duplicate of 33206 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•