On Oct 24, 1:57 am, Michael Pavling wrote:
> Well, it is Saturday - don't people deserve a day off! :-) and... I
> hazard a guess that the tone of your original posts *may* have
> dissuaded some people from attempting to help... just a thought. NOI.
My apologies for impoliteness in the original
On Oct 24, 12:46 am, Michael Pavling wrote:
> On 23 October 2010 16:34, Cocy N wrote:
> Multipart data has to be turned into something... if you post a mix of
> text fields and files, if one of those files is a text file, both
> content-types would be "text/plain", so h
On Oct 24, 12:25 am, Michael Pavling wrote:
> On 23 October 2010 16:05, Cocy N wrote:
> BTW Did *you* read RFC 2388 rather than just punting on the assertions
> from the Stackoverflow post? I quote: "As with all multipart MIME
> types, each part has an optional 'Content-T
On Oct 23, 11:04 pm, Michael Pavling wrote:
> > On Oct 17, 1:45 am, Cocy N wrote:
> >> As mentioned below, ruby on rails does not seems to treat the
> >> multipart form posts as based in RFC 2388.
> >> e.g. .Each part of a multipart/form-data is supposed to have
On Oct 23, 11:04 pm, Michael Pavling wrote:
> > On Oct 17, 1:45 am, Cocy N wrote:
> >> As mentioned below, ruby on rails does not seems to treat the
> >> multipart form posts as based in RFC 2388.
> >> e.g. .Each part of a multipart/form-data is supposed to ha
Okay, nobody in rails communication try to let rails follow RFC 2388.
I won't use rails anymore. It's sucks!
On Oct 17, 1:45 am, Cocy N wrote:
> As mentioned below, ruby on rails does not seems to treat the
> multipart form posts as based in RFC 2388.
> e.g. .Each part of a
As mentioned below, ruby on rails does not seems to treat the
multipart form posts as based in RFC 2388.
e.g. .Each part of a multipart/form-data is supposed to have a content-
type.
<
http://stackoverflow.com/questions/1947315/load-testing-multipart-form/3949624#3949624
>
I have a problem on si
7 matches
Mail list logo
