Re: Using Httpwebrequest to Submit multipart/form-data
From: Joerg Jooss (joerg.jooss_at_gmx.net)
Date: 10/18/04
- Next message: Brad Shook: "Re: reloading app.config in Configuration Management Application Block ???"
- Previous message: Curt86: "Re: Compiling/Linking old C code in .NET"
- In reply to: Gregory A Greenman: "Re: Using Httpwebrequest to Submit multipart/form-data"
- Next in thread: Sean McCormack: "RE: Using Httpwebrequest to Submit multipart/form-data"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 18 Oct 2004 22:40:46 +0200
Gregory A Greenman wrote:
> In article <#XBzNBGtEHA.1336@tk2msftngp13.phx.gbl>,
> joerg.jooss@gmx.net says...
[...]
>> There's no defined order in which form parameters are to be sent, so
>> that shouldn't make a difference. If a web application does assume a
>> specific order, it's broken.
>
>
> I can't seem to find any equivalent for multipart forms, but
> according to RFC 1866 browsers should list the parameters in the
> same order they appear in in the form.
>
> 8.2.1.2:
> "The fields are listed in the order they appear in the document
> with the name separated from the value by `=' and the pairs
> separated from each other by `&'. Fields with null values may be
> omitted."
>
> http://www.faqs.org/rfcs/rfc1866.html
You're right! I was stuck in my own little word of
application/x-www-form-urlencoded ;-)
That's what happnes once you got used not to rely on parameter ordering due
to the way the Servlet API or ASP.NET work...
Cheers,
-- Joerg Jooss www.joergjooss.de news@joergjooss.de
- Next message: Brad Shook: "Re: reloading app.config in Configuration Management Application Block ???"
- Previous message: Curt86: "Re: Compiling/Linking old C code in .NET"
- In reply to: Gregory A Greenman: "Re: Using Httpwebrequest to Submit multipart/form-data"
- Next in thread: Sean McCormack: "RE: Using Httpwebrequest to Submit multipart/form-data"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|