From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mx.sdf.org ([205.166.94.20]) by ewsd; Sun Mar 22 17:37:39 EDT 2020
Received: from [192.168.0.16] (c-98-212-152-230.hsd1.il.comcast.net [98.212.152.230])
	(authenticated (0 bits))
	by mx.sdf.org (8.15.2/8.14.5) with ESMTPSA id 02MLbPLX006901
	(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128 bits) verified NO);
	Sun, 22 Mar 2020 21:37:26 GMT
Date: Sun, 22 Mar 2020 16:37:19 -0500
User-Agent: K-9 Mail for Android
In-Reply-To: <2B6017B9-7663-48BD-B64C-C4F1CB9F8036@sdf.org>
References: <6F9D014DB661B27EC9A9E01FC38B1485@gmail.com> <2B6017B9-7663-48BD-B64C-C4F1CB9F8036@sdf.org>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9front] [PATCH] netsurf: webfs POST implementation
To: 9front@9front.org, telephil9@gmail.com
From: Kyle Nusbaum <knusbaum@sdf.org>
Message-ID: <66D5F098-AD57-4F3E-80EE-4A77CA375074@sdf.org>
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: lossless immutable information method callback configuration solution 

That said, we *know* we're getting these handle exhaustion errors=2E I thin=
k we can merge this now, and if we start seeing header errors, we can fix t=
hat then=2E

On March 22, 2020 2:25:57 PM CDT, Kyle Nusbaum <knusbaum@sdf=2Eorg> wrote:
>Thanks a bunch!
>
>The only hesitation I have is with the closing of the body when data is
>finished=2E This frees the webfs handle, but if netsurf tries to read any
>headers after, it will encounter errors=2E Maybe it is not doing that,
>but I don't see any reason why it couldn't do that=2E
>
>
>On March 21, 2020 2:17:04 PM CDT, telephil9@gmail=2Ecom wrote:
>>Hi,
>>
>>Here is a patch to implement POST requests in netsurf webfs fetcher=2E
>>I could not test multipart POST requests yet as I could not find a
>site
>>that uses this encoding method=2E
>>Also, the webfs clients exhaustion issue should now be fixed=2E
>>
>>Regards,
>>Philippe
>
>-- Kyle

-- Kyle