[Tizen Application-dev] SECURITY_ERR: DOM Exception 18

Ryan Ware ware at linux.intel.com
Wed Feb 15 23:39:14 GMT 2012



> -----Original Message-----
> From: application-dev-bounces at lists.tizen.org [mailto:application-dev-
> bounces at lists.tizen.org] On Behalf Of Denis Sapon
> Sent: Tuesday, February 14, 2012 12:44 PM
> To: Schaufler, Casey
> Cc: application-dev at lists.tizen.org
> Subject: Re: [Tizen Application-dev] SECURITY_ERR: DOM Exception 18
> 
> Thank you for your reply. But there remains another question. Why do I
> get same-origin policy exception when work with WebSQL, in particular
> when I second time call openDatabase function or try SQL transaction

My guess would be that you're doing something that inadvertently changes
either protocol, hostname or port.  However, that's just a guess since I
can't see your code.

Ryan

> 2012/2/14 Schaufler, Casey <casey.schaufler at intel.com>:
> >> -----Original Message-----
> >> From: application-dev-bounces at lists.tizen.org [mailto:application-dev-
> >> bounces at lists.tizen.org] On Behalf Of Denis Sapon
> >> Sent: Tuesday, February 14, 2012 3:52 AM
> >> To: application-dev at lists.tizen.org
> >> Subject: [Tizen Application-dev] SECURITY_ERR: DOM Exception 18
> >>
> >> Hi,
> >>
> >> I have a project written in html and javascript. I tried to use it
> >> with Tizen SDK and it work with Tizen IDE html preview, but not work
> >> with emulator. I got exception with message "SECURITY_ERROR: DOM
> >> Exception 18" when send ajax request or when try open database.
> >>
> >> The first part of the problem partially solved when I added access tag
> >> into config.xml. But this approach does not suit me, because I have to
> >> explicitly specify origin. Is there a way to dynamically specify
> >> origin from code?(not from config.xml)
> >
> > No. Absolutely not.
> >
> > Imagine a good application that gets compromised by an evil
> > hacker. The compromised application might try to send private
> > information somewhere that the evil hacker could access it.
> > If the compromised application gets a security denial today
> > the private information is safe. If the application could
> > simply turn around and tell the system that it should have
> > the denied access just because it wants it now the ill gotten
> > information can flow freely into the evil hacker's hands and
> > there is nothing that a good programmer can do to stop it.
> >
> > Remember that what is convenient for the good programmer is
> > often enabling for the evil programmer.
> >
> >> The second part of the problem, I do not understand and would
> >> appreciate any hint
> >>
> >>
> >> --
> >> --Thanks,
> >> Denis
> >> _______________________________________________
> >> Application-dev mailing list
> >> Application-dev at lists.tizen.org
> >> https://lists.tizen.org/listinfo/application-dev
> 
> 
> 
> --
> --Thanks,
> Denis
> _______________________________________________
> Application-dev mailing list
> Application-dev at lists.tizen.org
> https://lists.tizen.org/listinfo/application-dev



More information about the Application-dev mailing list