Hello, I've just spent a couple of hours playing with the new release candidate of prototype, and I've noticed some odd behavior when using Ajax.Request to post form data. I have a couple of example scripts here:
http://www.straightnochaser.org/test/test.html - using RC2 http://www.straightnochaser.org/test/test.html - using 1.5.0 I know the onComplete doesn't totally work in the second example, but that's not the issue. Open those URLs in firefox with firebug installed, and take a look at the 'post' tab. You should see that is sent as a query string in the first example, but as a key:value pair in the second. I am entering the postBody into the options the same way in both examples, and I took a look at the code of prototype itself in both script versions, but I can't see any code that acts on it differently in each. Why does it post differently? Did I not set a new variable correctly? The real reason I ask is that I am using prototype with a custom-built python framework (not built by me) and most of the backend was written to look for post varibles using the original key:value pairs, and it now fails with the new method (error 501). It could be re-written, but the time and cost would be less than ideal, so I would like to make sure this is behavior-as-designed by prototype, and not a bug or something. Though any info on how to fix this on the front-end would be appeciated as well. Thanks, -Tom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
