Closed Bug 202725 Opened 19 years ago Closed 19 years ago
Elements By Tag Name (or similar) on SOAP response gives "permission denied" JS error
That's just a standard security exception you get when you try to read the contents of something off your server via the DOM....
That's fair enough, but the script allows for that by enabling UniversalBrowserRead. I've tried mucking about with all the security settings that seem appropriate, up to and including enabling allAccess, but can't get the exception to go away. The script ought to work as is.
Over to Web Services.
Assignee: dom_bugs → harishd
Status: UNCONFIRMED → NEW
Component: DOM Core → Web Services
Ever confirmed: true
QA Contact: desale → ashishbhatt
The test case fails (ie nothing happens - with the corresponding js error) on the nightly build 20030421 for linux too. I haven't been able to satisfy mozilla by requesting permissions with PrivilegeManager either. I have also seen "Access to property denied" code: "1010" nsresult: "0x805303f2 (NS_ERROR_DOM_PROP_ACCESS_DENIED)" in my various attempts with this. Thanks
Another thing I discovered in my efforts. I can display the same soap response that throws the js error with various DOM methods by calling: new XMLSerializer().serializeToString(soap_response.message); on it with no problems.
taking SOAP bugs.
Assignee: harishd → jgaunt
Taking the bug back since I'm already working on it.
Assignee: jgaunt → harishd
The patch in bug 193953 should fix the problem. I've landed the fix on the trunk. The attached test case works fine for me. Reporter please confirm in tomorrow's mozilla trunk.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.