# Re: URLs Containing "#"

Reinier Post (reinpost@win.tue.nl)
Thu, 8 Jun 1995 05:47:16 +0500

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Erik Jul: "Re: OCLC's URN Services Proposal"
- Previous message: Paul Hoffman: "Re: OCLC's URN Services Proposal"

    Date: Thu, 8 Jun 1995 05:47:16 +0500

    Message-Id: <199506080848.KAA19115@wsinis10.win.tue.nl>

    From: reinpost@win.tue.nl (Reinier Post)

    To: Multiple recipients of list <www-proxy@www10.w3.org>

    Subject: Re: URLs Containing "#"

You (Randy Simons) write:

>Or, would it be better to tell the gophermaster at 146.138.63.106 that "#"
>is a reserved character (in URLs) and shouldn't be used in filenames?

Yes, definitely. Meanwhile, I've seen some problems reported with the way
the CERN proxy handles URLs. The problem is that software tends to escape
and unescape special characters in URLs; the proxy software appears to do
this in places, causing URLs with special characters in their path component
to be seen as identical to URLs in which these special characters are
escaped. The standard does not guarantee this identity. If you want to, I
can probably look up the details.

    --
    Reinier Post						 reinpost@win.tue.nl
    a.k.a. <A HREF="http://www.win.tue.nl/win/cs/is/reinpost/">me</A>
    [LINK] [LINK] [LINK] [LINK] [LINK] [LINK] [LINK] [LINK] [LINK] [LINK] [LINK]

- Next message: Erik Jul: "Re: OCLC's URN Services Proposal"
- Previous message: Paul Hoffman: "Re: OCLC's URN Services Proposal"