I ran into the same problem because I probably found the same example you did, which was built for use with Perl, not Rails. Perl is apparently more tolerent of simple formatting errors, which is not surprising considering Larry Wall's philosophy.The example contains a line similar to this:
[ body appendData:[[NSString stringWithFormat:@"\r\n...@\r \n",boundary] dataUsingEncoding:NSUTF8StringEncoding]]; It turns out that is wrong. The initial \r\n should not be there, so you should have: [ body appendData:[[NSString stringWithFormat:@"-...@\r\n",boundary] dataUsingEncoding:NSUTF8StringEncoding]]; Once I made that change, everything worked perfectly. Hope that helps someone. D On Jan 31, 5:49 pm, Kelly Sutton <[email protected]> wrote: > Can you please explain what the problem was and your solution? > > I'm having the same one. > > On Dec 3 2008, 7:15 am, Ivan Evtuhovich <[email protected]> wrote: > > > Sorry, this was problem in our programmers in other department, we > > solve this problem. > > > Thanx you for help. > > > On Dec 3, 6:13 pm, "Mislav Marohnić" <[email protected]> > > wrote: > > > > 2008/12/3 Ivan Evtuhovich <[email protected]> > > > > > I understand, but it is imposible to fix Apple library. > > > > Well, you can contribute a failing test and a patch to Rails yourself. > > > This > > > wouldn't be the first time Rails fixed a badly implemented HTTP spec by > > > Apple. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
