Re: [web2py] AJAX weirdness

2011-10-19 Thread Harshad
Makes sense. Thanks.

Re: [web2py] AJAX weirdness

2011-10-19 Thread Anthony
On Wednesday, October 19, 2011 11:29:15 AM UTC-4, rochacbruno wrote: > > On Wed, Oct 19, 2011 at 1:13 PM, Harshad wrote: > >> Before we close this thead, I am curious as to why/how is this a security >> risk? > > > Having a controller which returns nothing > > def index(): > return dict() > >

Re: [web2py] AJAX weirdness

2011-10-19 Thread Bruno Rocha
On Wed, Oct 19, 2011 at 1:13 PM, Harshad wrote: > Before we close this thead, I am curious as to why/how is this a security > risk? Having a controller which returns nothing def index(): return dict() and for example in session. session.mysecretvariable = "hello" If the index controller

Re: [web2py] AJAX weirdness

2011-10-19 Thread Harshad
Before we close this thead, I am curious as to why/how is this a security risk?

Re: [web2py] AJAX weirdness

2011-10-19 Thread Harshad
Thanks to rochacbruno and Anthony, I was able to solve this problem. All I did was include the line response.generic_patters=[*] in db.py.

Re: [web2py] AJAX weirdness

2011-10-18 Thread Anthony
If you're using generic.json for the view, then setting response.generic_patterns might be the issue. The 'welcome' app allows the generic views to work on the local machine only by default. If you have a specific get_response.json view, then this would not be the issue. Anthony On Tuesday, Oc

Re: [web2py] AJAX weirdness

2011-10-18 Thread Harshad
I'm at home right now, but I'll try that at work tomorrow. Thanks.

Re: [web2py] AJAX weirdness

2011-10-18 Thread Bruno Rocha
response.generic_patterns = ['*'] or ['.json']

[web2py] AJAX weirdness

2011-10-18 Thread Harshad
Following is the code that makes the ajax call: $.ajax({ type: "GET", url: '/devicemanager/default/get_response.json/192.168.1.24/107', success: display_received, }); display_received displays the received information. The controller simply does the following: de