Really my issue is with sending to the test web server that is setup with cucumber -- I'm pretty sure that curb is doing the right thing, it's just that I'm not giving it enough to make the connection. I imagine I'd have the same issue with Net::HTTP or anything else I tried to use. There's something going on in cucumber that I don't know about. Well, there's a lot going on that I don't know about, tbh ... :)
On 23 February 2010 22:18, Alex Barlow <[email protected]> wrote: > It doesnt actually, it was to be honest, designed for really quick xml > getting. But the code is so easy to extend. > > Another good one is either activeresource or right_httpconntection > > On 23 Feb 2010, at 20:32, doug livesey wrote: > > Thanks Alex -- I'll have a look. > Does it handle put, delete and the rest, too? It doesn't seem to from a > first quick look at the source. > Cheers, > Doug. > > On 23 February 2010 19:30, Alex Barlow <[email protected]> wrote: > >> I have a gem for curl. <Http://github.com/arbarlow/rubycurl> >> Http://github.com/arbarlow/rubycurl >> >> See how that fairs? >> >> Sent from my iPhone >> >> On 23 Feb 2010, at 12:48, doug livesey <[email protected]> wrote: >> >> Hi -- I'm finding that post() is serialising my json data badly, so for >> that and other reasons, I want to use curl to test my web service in >> cucumber. >> (I'm using capybara, btw.) >> The problem is, on a service that I already know is working fine, I'm >> getting this in the body of the failed attempt to post: >> "The requested URL /mobile_app/timesheet_uploads.json was not found on >> this server." >> >> The code that generates that error is: >> curl = Curl::Easy.new( mobile_app_timesheet_uploads_url( :format => >> "json" ) ) >> curl.http_post( { upload_data: @upload_data }.to_json ) >> puts curl.body_str >> >> From my (I guess not particularly strong) understanding of what happens in >> cucumber, this should work, so I'm stumped. >> Can anyone advise me on how to get this to work? >> Cheers, >> Doug. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "NWRUG" 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/nwrug-members?hl=en. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "NWRUG" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<nwrug-members%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/nwrug-members?hl=en. >> > > > -- > You received this message because you are subscribed to the Google Groups > "NWRUG" 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/nwrug-members?hl=en. > > > -- > You received this message because you are subscribed to the Google Groups > "NWRUG" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<nwrug-members%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/nwrug-members?hl=en. > -- You received this message because you are subscribed to the Google Groups "NWRUG" 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/nwrug-members?hl=en.
