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 23 October 2010 17:28, Cocy N wrote:
> BTW, thanks for your reply.
You're welcome. After thinking about it for a bit, it *is* an interesting issue.
> You are the only one who replied to my post :)
Well, it is Saturday - don't people deserve a day off! :-) and... I
hazard a guess that the t
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 how would a server know whi
On 23 October 2010 16:34, Cocy N wrote:
> I quote :
> "4.5 Charset of text in form data
> Each part of a multipart/form-data is supposed to have a content-type."
Yes, I saw that too... and wondered if it was arguable that the RFC
contradicts itself.
But as far as I can rationalise:
Multipart
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-Type'". Optional
I
On 23 October 2010 16:05, Cocy N wrote:
> Have you read the URL page that I've posted?
Yes. IIRC, the OP complained that Rails worked perfectly from his
browser, but when using some testing software, the results were not
the same.
> If so, how come you don't understand what the author of the pag
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 a content-
> >> type.
> Have you 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 a content-
> >> type.
>
> Have you
> 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 a content-
>> type.
Have you tried it? Works okay for me. I've just created a form wit
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 multipart/form-data is
10 matches
Mail list logo
