Re: [nodejs] 'ran insecure content' error from Node web service

2013-08-11 Thread Johnathan Mercer
Hi Abhay, Using https in the ajax actually breaks it (just tried), I think you need to do what Jose has suggested. On Sunday, August 11, 2013 10:38:52 AM UTC-4, Abhay Rana wrote: > > Make the request to /wines over https instead of http. > > -- > Abhay Rana > http://about.me/n3m0 > > > On Sun,

Re: [nodejs] 'ran insecure content' error from Node web service

2013-08-11 Thread Jose Luis Rivas
On 8/11/13 7:37 AM, Johnathan Mercer wrote: > Hi Jose, > YES, that worked! It returns the data but I still get a console warning: > > The page at [my url] displayed insecure content from > http://69.173.71.80:3000/wines. > > Do you know how to avoid this warning? > That warning is when you lo

Re: [nodejs] 'ran insecure content' error from Node web service

2013-08-11 Thread Abhay Rana
Make the request to /wines over https instead of http. -- Abhay Rana http://about.me/n3m0 On Sun, Aug 11, 2013 at 8:07 PM, Johnathan Mercer wrote: > Hi Jose, > YES, that worked! It returns the data but I still get a console warning: > > The page at [my url] displayed insecure content from > htt

Re: [nodejs] 'ran insecure content' error from Node web service

2013-08-11 Thread Johnathan Mercer
Hi Jose, YES, that worked! It returns the data but I still get a console warning: The page at [my url] displayed insecure content from http://69.173.71.80:3000/wines. Do you know how to avoid this warning? On Sunday, August 11, 2013 10:28:47 AM UTC-4, Johnathan Mercer wrote: > > I'll try it

Re: [nodejs] 'ran insecure content' error from Node web service

2013-08-11 Thread Johnathan Mercer
I'll try it out thanks!! On Sunday, August 11, 2013 10:22:00 AM UTC-4, Jose Luis Rivas wrote: > > On Sun Aug 11 07:14:58 2013, Johnathan Mercer wrote: > > Hi Jose, > > Thanks for the fast response! Can you elaborate? I don't quite > > understand.. > > John > > > > On Sunday, August 11, 2013

Re: [nodejs] 'ran insecure content' error from Node web service

2013-08-11 Thread Jose Luis Rivas
On Sun Aug 11 07:14:58 2013, Johnathan Mercer wrote: > Hi Jose, > Thanks for the fast response! Can you elaborate? I don't quite > understand.. > John > > On Sunday, August 11, 2013 9:37:54 AM UTC-4, Jose Luis Rivas wrote: > > I think you are missing the OPTIONS. That's the method sent on the >

Re: [nodejs] 'ran insecure content' error from Node web service

2013-08-11 Thread Johnathan Mercer
Hi Jose, Thanks for the fast response! Can you elaborate? I don't quite understand.. John On Sunday, August 11, 2013 9:37:54 AM UTC-4, Jose Luis Rivas wrote: > > I think you are missing the OPTIONS. That's the method sent on the > pre-flight by the browser. > > On 8/11/13 5:52 AM, Johnathan Mer

Re: [nodejs] 'ran insecure content' error from Node web service

2013-08-11 Thread Jose Luis Rivas
I think you are missing the OPTIONS. That's the method sent on the pre-flight by the browser. On 8/11/13 5:52 AM, Johnathan Mercer wrote: > I successfully implemented a service locally but when I try to implement > on my VM I get: > > [blocked] > The page at [myurl;)] ran insecure content

[nodejs] 'ran insecure content' error from Node web service

2013-08-11 Thread Johnathan Mercer
I successfully implemented a service locally but when I try to implement on my VM I get: [blocked] The page at [myurl;)] ran insecure content from http://69.173.71.80:3000/wines? callback=jQuery19107150888352189213_1376159198745&_=1376159198746. I tried adding: var allowCrossDo