search for: bad_request

Does anyone have an example of using REST and submitting data through a POST operation and then possibly loading that data with activerecord. Also, if you have client code written in another language (java,.net, C), would you have that code as well? Berlin Brown

I want to create a route for any image. This is in order to create an email report explaining what the missing image is. I could create a route for each directory that currently has images in it but wanted something more general like: map.connect "/**/*.gif", :controller => ''image_handler'', :action => ''handle_image'' Which doesn''t

Hi I am running ruby 1.8.4 and rails 1.0.0 with Apache 2. I made a simple rails application called demo and also created a controller called say and an action called hello which is working fine using webrick. To run it under Apache I created a symlink demo1 which is linked to the demo/public directory. If I run it using www.example.com/demo1 then I get the "Rails- Welcome Aboard"

...Project.should_receive(:create).with(project_params) req = fake_request req[:project] = project_params controller, action = post(''/projects'', :fake_request => req) end end Now my action doesn''t even get called. the value of action is ''bad_request'', probably because the fake request I created doesn''t have all the right stuff. I can''t for the life of me grok how I send in "form" values to a POST action from a spec and could use some help here. If someone can explain to me the intended behaviour I can subm...

I''ve set up a route like this map.connect ''confirm/:id/:full_name/'', :controller => "users", :action => "confirm" and I''m wondering what is the best way to verify in the confirm method. full_name created in the model and it''s not in the database. This doesn''t work because it doesn''t parse one, then the

...at ActionController::TestCase.get() method ignores what I have in routes.rb. Happens in 3.0.10 and 3.1.0 too. I have the following RSpec2 test of my XmlRpcController#index action: it "should get nothing in response to GET request" do get :index response.response_code.should == 400 #bad_request end And the only line related to this route in routes.rb is: post ''rpc'', :to => "xml_rpc#index" ''rake routes'' also shows only this route defined. As a result when I run this test that action actually DOES get executed! I judge this by putting a...

...ready initialized constant MOVED_TEMPORARILY /usr/local/lib/ruby/gems/1.8/gems/httpclient-2.1.5.2/lib/httpclient/http.rb:29: warning: already initialized constant TEMPORARY_REDIRECT /usr/local/lib/ruby/gems/1.8/gems/httpclient-2.1.5.2/lib/httpclient/http.rb:30: warning: already initialized constant BAD_REQUEST /usr/local/lib/ruby/gems/1.8/gems/httpclient-2.1.5.2/lib/httpclient/http.rb:31: warning: already initialized constant UNAUTHORIZED /usr/local/lib/ruby/gems/1.8/gems/httpclient-2.1.5.2/lib/httpclient/http.rb:32: warning: already initialized constant PROXY_AUTHENTICATE_REQUIRED /usr/local/lib/ruby/ge...

Been trying to deploy my rails app on Redhat ES3, Apache2, FastCGI with Plesk all day. Fun stuff. Basically, the issue that I can not solve has to do with access to /public. None of my images, javascripts, etc. are working in the app. Trying to access any of these results in a 404 (or routing error if in developer mode). Oddly, the 404 file it displays is -- you guessed it -- in fact *in*

I am trying to come up with a workable solution in managing numerous Mac workstations allowing a high degree of flexibility with regards to certs. My puppet environment is setup to application installation on machines that have been ''imaged'' with a base OS and the puppet and facter apps. So, when a Mac is ''imaged'' and subsequently re-booted, puppet is run at