[jcifs] jcifs bug?

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

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

I can make my source work by writing an encoder that does not escape '/'.


More information about the jcifs mailing list