Subject:
|
Re: URL characters
|
Newsgroups:
|
lugnet.publish
|
Date:
|
Mon, 19 Jul 1999 19:05:08 GMT
|
Viewed:
|
4990 times
|
| |
|
|
In lugnet.publish, Larry Pieniazek writes:
> Universal Resource Locators (that's what it stands for) started out as
> path descriptions. For why twiddle is supported, you might read up on
> the Andrew File System.
>
> ~lpien is a valid file path (that is, you can cd to it) on a CTP unix
> box, or was until I resigned. At various times in my career there it
> resolved to various different places as my home directory got moved
> around from machine to machine.
>
> Therefore w3.ctp.com/~lpien is a valid URL if you're on the CTP internal
> network (the internal nameserver knows how to resolve w3.ctp.com)
>
> That's how I understood it.
Total grokkage there! (Been using ~ for that since '84 :) It's one of the
Truly Great Simplicities of modern day computing life, IMHO.
> If url's disallowed twiddle, I would consider them broken.
I think -that's- the key thing! (People considering it broken.) URLs & URIs
do disallow twiddle (ASCII 126) but nevertheless, I guess people all 'round
the world years must've banded together (or independently) said, "Hey, that's
majorly broken; URLs *should* allow twiddles, so I'm gonna use them anyway.
I'll even hack my local httpd and Mosaic to make it work if I have to." :-)
Mystery still remains why W3 still says twiddle (~) is disallowed in URLs. :)
--Todd
|
|
Message is in Reply To:
 | | Re: URL characters
|
| (...) That's what I thought the etymology of ~ was in URLs too -- but how did it ever get *allowed* in URLs in the first place? That's what baffles me. The first time someone tried it, why didn't it fail? The early browsers and httpd daemons must've (...) (25 years ago, 18-Jul-99, to lugnet.publish)
|
86 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
