This project is archived and is in readonly mode.
Bug in Chromium with GET parameters when doing a POST request
-
Joe None
Was having the exact same problem, thanks for posting this. Seems like jQuery shouldn't allow a call like this to happen, in my opinion.
-
Stefan Siebel
I was getting the same error message, however the root cause seemed to be another one. My URL looked like /my/url?locale=en. But when I removed the URL param I still got the same error.
It turned out that I was adding a parameter twice. Once by serializing the form and the second time by calling$(document).ajaxSend(function(event, request, settings) { settings.data = { someParam: "somevalue" }; });After removing these three lines things started working in Google Chrome.
-
Damien MATHIEU
bump !
This belongs in fact to jQuery. Not rails. Could someone close this ticket please ?
http://dev.jquery.com/ticket/5123it also appears if the data is undefined. We should then set it to null.
-
Erik St. Martin
- Tag changed from chromium, javascript, jquery, params to chromium, invalid, javascript, jquery, params
-
Yehuda Katz (wycats)
- State changed from new to open
- Tag changed from chromium, invalid, javascript, jquery, params to chromium, javascript, jquery, rails3
- Assigned user set to Yehuda Katz (wycats)
- Milestone cleared.
This is in fact a jQuery problem, but the Rails error could use some improvement (in general, failsafe errors mean that Rails didn't catch something it should have)
-
Repository
- State changed from open to resolved
(from [48c1d8c341e1fe09111424131f7d223ad032b7e1]) Provide a better error if the parsed REXML document has no root [#3803 Bug in Chromium with GET parameters when doing a POST request state:resolved] http://github.com/rails/rails/commit/48c1d8c341e1fe09111424131f7d22...