From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <476BE618.5040403@gmx.de> Date: Fri, 21 Dec 2007 17:13:12 +0100 From: Kernel Panic User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 MIME-Version: 1.0 To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] Abaco: url parsing problem References: <5d375e920712210739j27248993o683fa145a0bdcc8@mail.gmail.com> In-Reply-To: <5d375e920712210739j27248993o683fa145a0bdcc8@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 1f9c338a-ead3-11e9-9d60-3106f5b1d025 Uriel wrote: >That is why somebody (cough) riped out the url parsing code from webfs >and put it into a library, and then updated abaco to use that >library... but we all know here code and effort duplication is good, >so never mind. > > the browser needs to understand url-encoding anyway beacause he he needs to touch the url (build absolute urls from relatives in context of the fetched page). so having the lib in abaco is ok i think. but maybe other stuff could gain from webfs *fixing* urls. maybe some rc-scripts where you dont want to urlencode stuff first? for example you want to fetch a search-result page and dont want to urlencode your concatenated search query before passing it to webfs? makes that sense? ;-) >uriel > >On Dec 20, 2007 4:27 PM, Federico G. Benavento wrote: > > >>>Does webfs do the url parsing? or abaco before sending it to webfs, if so, maybe >>>the function can be fixed easily. >>> >>> >>I guess, my urlencode is broken, I'll fix it later >> >>thanks >> >>Federico G. Benavento >> >>--- >>/bin/fortune: >> >> >>Even the simplest solution is bound to have something wrong with it. >> >> -- cinap