From: Kyle Nusbaum <knusbaum@sdf.org>
To: 9front@9front.org, telephil9@gmail.com
Subject: Re: [9front] [PATCH] netsurf: webfs POST implementation
Date: Sun, 22 Mar 2020 14:25:57 -0500 [thread overview]
Message-ID: <2B6017B9-7663-48BD-B64C-C4F1CB9F8036@sdf.org> (raw)
In-Reply-To: <6F9D014DB661B27EC9A9E01FC38B1485@gmail.com>
Thanks a bunch!
The only hesitation I have is with the closing of the body when data is finished. This frees the webfs handle, but if netsurf tries to read any headers after, it will encounter errors. Maybe it is not doing that, but I don't see any reason why it couldn't do that.
On March 21, 2020 2:17:04 PM CDT, telephil9@gmail.com wrote:
>Hi,
>
>Here is a patch to implement POST requests in netsurf webfs fetcher.
>I could not test multipart POST requests yet as I could not find a site
>that uses this encoding method.
>Also, the webfs clients exhaustion issue should now be fixed.
>
>Regards,
>Philippe
-- Kyle
next prev parent reply other threads:[~2020-03-22 19:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 19:17 telephil9
2020-03-22 19:25 ` Kyle Nusbaum [this message]
2020-03-22 21:37 ` [9front] " Kyle Nusbaum
2020-03-22 22:14 ` telephil9
2020-03-22 2:11 kokamoto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2B6017B9-7663-48BD-B64C-C4F1CB9F8036@sdf.org \
--to=knusbaum@sdf.org \
--cc=9front@9front.org \
--cc=telephil9@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).