Forum



01:34

30/05/2012

I would just reply to my own post, but it has not yet been moderated, so I'll put this in to save any would-be helpers some time.
Our story so far: My Rails application's JQGrid's POST requests were running afoul of the OpenID mechanism, as if the browser session didn't belong to this user, or they hadn't authenticated with their OpenID Identity Provider. (You'll know if you're having the same problem if the last thing the browser sees is a 401 error.)
Basically, Sante at the OpenID Code list pointed me to the forgery-protection mechanism in Rails as the culprit. Sure enough, when I turned that off it worked. Of course you can't just leave it off, but I found a very nice fix at http://henrik.nyh.se/2008/05/r.....nbsp;which adds a handler for the ajaxSend event, ensuring that the Rails authenticity token is included with each and every Ajax request. One line in one file, seven in another, problem solved. Oh happy day! Thanks Sante and Henrik!
Most Users Ever Online: 715
Currently Online:
182 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
OlegK: 1255
markw65: 179
kobruleht: 144
phicarre: 132
YamilBracho: 124
Renso: 118
Member Stats:
Guest Posters: 447
Members: 11373
Moderators: 2
Admins: 1
Forum Stats:
Groups: 1
Forums: 8
Topics: 10592
Posts: 31289
Newest Members:
, razia, Prankie, psky, praveen neelam, greg.valainis@pa-tech.comModerators: tony: 7721, Rumen[Trirand]: 81
Administrators: admin: 66