From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from a-painless.mh.aa.net.uk ([81.187.30.51]) by ewsd; Sat Jan 4 05:21:57 EST 2020 Received: from 132.198.187.81.in-addr.arpa ([81.187.198.132] helo=quintile.net) by a-painless.mh.aa.net.uk with esmtp (Exim 4.92) (envelope-from ) id 1ingYr-0005I1-Ux for 9front@9front.org; Sat, 04 Jan 2020 10:21:38 +0000 Received: from [10.15.92.160] ([148.252.128.113]) by quintile.net; Sat Jan 4 10:21:37 GMT 2020 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Steve Simon Mime-Version: 1.0 (1.0) Subject: Re: [9front] Netsurf 3.9 for Plan 9 (work in progress) Date: Sat, 4 Jan 2020 10:21:35 +0000 Message-Id: References: In-Reply-To: To: 9front@9front.org X-Mailer: iPhone Mail (17C54) List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: core realtime full-stack optimizer hi, the response header fields are exposed as psudo-files in webfs, i cannot rem= ember the path just now, but its the per connection directory. cookies are handled by webfs when and a file server (cookiejar?) which shou= ld =E2=80=9Cjust work=E2=80=9D, it should hopefully be just a matter of remo= ving cookie support from netsurf. it would be exciting to have netsurf running on plan9, especially if the cha= nges where merged back into the mainline. -Steve > On 3 Jan 2020, at 8:15 pm, Kyle Nusbaum wrote: >=20 > =EF=BB=BFA shared repo would be nice.=20 >=20 > My attempt at using webfs has hit a snag, which is that webfs does not exp= ose the http response header in any way, as far as I can tell.=20 > I have it partially working in that it is getting and returning webpage da= ta, but netsurf wants the full response header.=20 >=20 > I think webfs is not the right solution for this. It is not the general-pu= rpose http service I thought it was. For this purpose, it has several issues= . It provides no access to the raw header bytes. We could still use it as a h= acky solution if we could reassemble the http header, but webfs mangles head= er names when creating the header files and leaves out cookies.=20 >=20 > However, since netsurf seems to do all the parsing of the response except s= eparating header from body, and delivers the request URL and post data in pr= e-packaged form, I think it's probably easier to just use a raw /net/tcp con= nection. >=20 >=20 > On January 2, 2020 9:30:50 PM CST, ori@eigenstate.org wrote: >>> Forgive me for any duplicates. I mistakenly sent a copy of this >>> mail with HTML. >>>=20 >>> This work is neat! >>>=20 >>> With Ori's changes I see the interface rendered. >>>=20 >>> I think the mouse handling is using absolute coordinates, because >>> the address bar only works if I position the window in the upper left >>> corner of my screen. >>>=20 >>> I can't get the program to actually render anything, even file:/// >>> resources, but I can see them getting fetched. >>>=20 >>> I get CSSBase displayed at the bottom of the screen, seeming to >>> correspond to the NSERROR_CSS_BASE error, but I can't figure out why >>> that's happening. I'm guessing that's why nothing is rendered, but >>> that may be a faulty assumption. >>=20 >> I also haven't seen them render, but I got it to show the ui before >> I had to run out the door, so I didn't try very hard.=20 >>=20 >>> The fetcher interface looks pretty straightforward and I think it >>> shouldn't be too difficult to write a webfs fetcher. I think I will >>> try that in my spare time. >>>=20 >>=20 >> Cool. >>=20 >> If we're going to have multiple people hacking on this, it >> probably makes sense to set up a git repository. >>=20 >> It'd be best to use upstream and fork a plan9 branch, so we can >> merge their changes and start upstreaming our local diffs more >> easily. >=20 > -- Kyle