From: Uriel <uriel99@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Abaco: url parsing problem
Date: Fri, 21 Dec 2007 11:40:00 -0500 [thread overview]
Message-ID: <5d375e920712210840j3a76a0c9o4e8b2d940be7e831@mail.gmail.com> (raw)
In-Reply-To: <476BE618.5040403@gmx.de>
On Dec 21, 2007 11:13 AM, Kernel Panic <cinap_lenrek@gmx.de> wrote:
> 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.
Lets not forget javascript and other such abominations.
And that is *precisely* why having two half broken sets of URL
parsing/manipulation code, one in webfs and one in abaco is so silly.
And why I factored out the url code in webfs and put it into a liburl,
and then modified abaco link against that instead of its own
simplistic and broken URL code.
The result has been on my sources/contrib dir for ages, why fgb has
not used it is beyond me.
uriel
> 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 <benavento@gmail.com> 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
>
>
next prev parent reply other threads:[~2007-12-21 16:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-20 9:37 pavlovetsky
2007-12-20 9:56 ` Federico G. Benavento
2007-12-20 11:22 ` Juan M. Mendez
2007-12-20 18:13 ` Lyndon Nerenberg
2007-12-20 21:22 ` Juan M. Mendez
2007-12-20 21:27 ` Federico G. Benavento
2007-12-21 15:39 ` Uriel
2007-12-21 16:13 ` Kernel Panic
2007-12-21 16:40 ` Uriel [this message]
2007-12-21 18:42 ` Juan M. Mendez
2007-12-21 16:35 ` David Leimbach
2007-12-21 16:43 ` Uriel
2007-12-21 16:55 ` roger peppe
2007-12-21 17:08 ` David Leimbach
2007-12-21 18:16 ` sqweek
2007-12-21 18:02 ` Wes Kussmaul
2007-12-21 18:17 ` ron minnich
2007-12-21 9:39 ` [9fans] " pavlovetsky
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=5d375e920712210840j3a76a0c9o4e8b2d940be7e831@mail.gmail.com \
--to=uriel99@gmail.com \
--cc=9fans@cse.psu.edu \
/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).