[jcifs] jcifs bug?

Bernie Wieser bernie.wieser at calgary.qcdata.com
Tue Feb 26 08:59:11 EST 2002


Except I have blurred 3.10 and 3.11 into one "intent".


-----Original Message-----
From: Christopher R. Hertel [mailto:crh at ubiqx.org]
Sent: Monday, February 25, 2002 2:57 PM
To: Bernie Wieser
Cc: James Nord; Michael B Allen; jcifs at samba.org
Subject: Re: [jcifs] jcifs bug?

On Mon, Feb 25, 2002 at 02:34:55PM -0700, Bernie Wieser wrote:
> Spec says protocol://[user@]host[:port]/fully_qualified_path
> (well, //<user>:<password>@<host>:<port>/<url-path> )
> Problem is, I just can't pass fully_qualified_path to URLEncoder.encode
> because the '/' will get escaped and then jcifs.UniAddress.getByName
> explodes again.  Spec says for files
>    Note that a slash "/" may appear in the <hsoname> without quoting and
>    no significance may be assumed by the application.  Though slashes
>    may indicate hierarchical structure on the server, such structure is
>    not guaranteed. Note that many <hsoname>s begin with a slash, in
>    which case the host or port will be followed by a double slash: the
>    slash from the URL syntax, followed by the initial slash from the
>    <hsoname>. (E.g., <URL:prospero://host.dom//pros/name> designates a
>    <hsoname> of "/pros/name".)
> (That example will cause jcifs to err on //host//file if I remember
> correctly.)
> I can make my source work by writing an encoder that does not escape '/'.

What section of the specification is this in?  I don't remember seeing
this.  Which RFC are you reading?

Chris -)-----

Samba Team -- http://www.samba.org/     -)-----   Christopher R. Hertel
jCIFS Team -- http://jcifs.samba.org/   -)-----   ubiqx development, uninq.
ubiqx Team -- http://www.ubiqx.org/     -)-----   crh at ubiqx.mn.org

More information about the jcifs mailing list