From: Martin Kraemer <Martin.Kraemer@mch.sni.de>
Message-Id: <199708221418.QAA08362@deejai.mch.sni.de>
Subject: Re: Spaces in Win32 executable names
To: new-httpd@apache.org
Date: Fri, 22 Aug 1997 16:18:21 +0200 (MET DST)
In-Reply-To: <3.0.3.32.19970822150603.012ee1b4@xxlink.nl> from Elizabeth
 Mattijsen at "Aug 22, 97 03:06:03 pm"
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

Elizabeth Mattijsen wrote,
> Wouldn't it make sense then to indeed only check the requested filename
> with the long filename and not allow any munged filenames as a requested
> filename at all?

That would be what I'd propose.
If one ever needs to access "old" files, there's no problem either
because their short name==long name (minus possible case difference).

The original problem, if I followed the thread correctly, was that when
executing (CGI-?) programs, windows experiences bugs when long program
names are used.

However, when doing this...:

  C> copy \command.com "not a shell.com"
  1 File(s) copied

  C> "not a shell"  /c dir
  NOTASH~1.COM      95.382  21.10.96   7:04 not a shell.com

we can see that programs with spaces in their names can be executed, too.

    Martin
-- 
| S I E M E N S |  <Martin.Kraemer@mch.sni.de>  |      Siemens Nixdorf
| ------------- |   Voice: +49-89-636-46021     |  Informationssysteme AG
| N I X D O R F |   FAX:   +49-89-636-44994     |   81730 Munich, Germany
~~~~~~~~~~~~~~~~My opinions only, of course; pgp key available on request