On Wednesday, June 5, 2019 at 12:47:51 PM UTC-7, Dave S wrote: > > > > On Wednesday, June 5, 2019 at 3:30:46 AM UTC-7, Val K wrote: >> >> Yes, file:// is even another protocol, so using http transport in this >> case is out of all standards. But it should work fine with regular web2py >> app (over http) > > > Since I found a way to successfully demonstrate the javascript working, it > is quite possible I will not ever pursue the file:// x-site issues. I've > done OPTIONS handling in node.js before, and I think I can see how to do it > in the front end (nginx), but I don't have a reason to pursue it at present. > > /dps > >
Although looking through some of my long-open tabs, I see mcm's cors_origin decorator from October '16, and curiosity might provoke me. -d -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/ac268300-8ec7-4f4d-9d3b-9ffbe7f12f4f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
