From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sat, 3 Mar 2007 11:08:32 -0500 From: Kris Maglione To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] httpd and %20 Message-ID: <20070303160832.GC41024@kris.home> References: <20070303114123.GB41024@kris.home> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="H8ygTp4AXg6deix2" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) Topicbox-Message-UUID: 17797d44-ead2-11e9-9d60-3106f5b1d025 --H8ygTp4AXg6deix2 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Mar 03, 2007 at 07:54:07AM -0800, Skip Tavakkolian wrote: >> Is there some reason that we should know of such superfluous javascript= =20 >> and inline CSS noise? > >i'll take a colorful description over unhelpful snarky diatribe. Snarky diatribe or not, it's still valid. Why do we need to see 3 lines=20 of noisy, superfluous data, with the relevant bit stuck in the middle?=20 Worse, the link contained javascript events that could have, for all I=20 know, not knowing their functions, interfered with the functioning of=20 the link. Regardless, the whole URL and its source in iweb is entirely=20 irrelevant to the issue: httpd doesn't seem to handle %20 correctly.=20 Why couldn't the testcase have been something simple and obvious, rather=20 than a bloated piece of HTML? At any rate, it was not intended as unhelpful diatribe. I don't care=20 much if people want to use all of the ugly features of HTML and the "Web=20 2.0", but I'd prefer not to run across it when I'm reading 9fans. Plan 9=20 is the one sane corner of the computer world that I can take solace in.=20 I know that I'm not the only one who feels this way, and I meant it as a=20 sincere request for courtesy. --=20 Kris Maglione Just because you are paranoid doesn't mean "they" aren't out to get you. --H8ygTp4AXg6deix2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.2 (FreeBSD) iD8DBQFF6Z2AseQZD8Aui4wRAmm5AJ99trrEz20zVI20wwK/rY2Tw3FcAACfSt9a +9olkZ4cxFaojPOdFxSZTss= =Uarx -----END PGP SIGNATURE----- --H8ygTp4AXg6deix2--