From: Karl Kleinpaste <karl@lycos.com>
Subject: Re: still one smiley glitch
Date: 17 Jul 1996 21:37:38 +0200 [thread overview]
Message-ID: <wiyraqa3c3h.fsf@gorilla.eng.lycos.com> (raw)
In-Reply-To: Richard Pieri's message of 17 Jul 1996 14:40:09 -0400
Richard Pieri <ratinox@unilab.dfci.harvard.edu> writes:
> That would be because "<colon><slash>" is *NOT* a valid URL component.
> It must be a colon followed by two slashes.
Yup, my error. I hadn't quite noticed that the 2nd URL was malformed.
next prev parent reply other threads:[~1996-07-17 19:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-17 17:25 Karl Kleinpaste
1996-07-17 18:40 ` Richard Pieri
1996-07-17 19:37 ` Karl Kleinpaste [this message]
1996-07-17 18:49 ` William Perry
1996-07-17 19:10 ` Per Abrahamsen
1996-07-17 19:43 ` Kai Grossjohann
1996-07-18 13:40 ` Richard Pieri
1996-07-18 13:44 ` Lars Balker Rasmussen
1996-07-18 14:06 ` Greg Thompson
1996-07-18 14:08 ` Per Abrahamsen
1996-07-18 17:20 ` Richard Pieri
1996-07-18 19:37 ` Greg Thompson
1996-07-19 14:17 ` Richard Pieri
1996-07-19 20:24 ` Steven L Baur
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=wiyraqa3c3h.fsf@gorilla.eng.lycos.com \
--to=karl@lycos.com \
/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).