From: Kris Maglione <bsdaemon@comcast.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] httpd and %20
Date: Sat, 3 Mar 2007 06:41:23 -0500 [thread overview]
Message-ID: <20070303114123.GB41024@kris.home> (raw)
In-Reply-To: <13426df10703030154t6be71308i4f73542c8f0defbe@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]
On Sat, Mar 03, 2007 at 02:54:46AM -0700, ron minnich wrote:
>I have a url, produced from iweb, that is this:
><a style="display: block; height: 24px; left: 463px; position:
>absolute; top: 0px; width: 63px; z-index: 2; "
>onmouseout="NBmouseout('3');" href="SC%202006.html"
>onmouseover="NBmouseover('3');"></a>
Is there some reason that we should know of such superfluous javascript
and inline CSS noise? It would be kinder to those of us who would like
to forget that such things as JS, inline CSS and, indeed, even SGML,
exist, yet still beleive that Plan 9 should have a well functioning http
server, if you left such things out. It would also be more helpful if
you gave a more direct example with less interfering factors. For
instance:
hget 'http://localhost/SC%202006.html'
Or, even better, in the way of ruling out interference:
{ dir=/net/tcp/^`{read}
echo connect 127.0.0.1!80 >$dir/ctl
cat <<! >$dir/data
cat $dir/data
} </net/tcp/clone
GET /SC%202006.html HTTP/1.1
Host: foo.com
!
Incidentally, I think that I'm coming off harsher than I intend, but I
haven't been able to sleep tonight.
--
Kris Maglione
If you can't convince them, confuse them.
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2007-03-03 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-03 9:54 ron minnich
2007-03-03 11:41 ` Kris Maglione [this message]
2007-03-03 15:54 ` Skip Tavakkolian
2007-03-03 16:08 ` Kris Maglione
2007-03-03 19:33 ` ron minnich
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=20070303114123.GB41024@kris.home \
--to=bsdaemon@comcast.net \
--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).