On Sun, Feb 10, 2008 at 11:42:10PM +0000, place wrote:
Currently, dillo always submits forms using url encoding regardless of the encoding specified by the form. Wikipedia, for example, specifies multipart/form-data because the user may submit huge blocks of text in languages where url encoding will be very inefficient.
OK, committed.
- This patch always uses the same boundary, but a different one REALLY should be used for every form submission. At the least, the string should be scrambled up somehow.
Yes, please finish that part. Probably checking the boundary string against URL_DATA, with strstr is a good idea too.
- It adds a URL_MultipartEnc flag. - For the Content-type header, I pull the boundary out of URL_DATA because I didn't want to clutter up the URL with a field for something not commonly used.
OK. -- Cheers Jorge.-