Yes but isn't this attitude sort of like going blindly into the night?
Clearly it is a concern of at least on person and, like cock roaches, where
there's one there are many. I always thought that forcing case sensitivity in
the url was just plane stupid, especially since DNS is not case sensitive.
On the other hand I can see where case sensitivity does offer benefits. But
Im not sure I can see where the benefits out way the problems.
Ideally there should be a way to ignore case on a per URL( read directory )
basis. This would ideally be an option in the OS. But since we cant rely on
that we should look to Apache source. If I was more of a programmer I would
gladly volunteer for this mod.
Being able to ignore case would make it a heck of a lot easier to migrate
web sites from NT to UNIX and back. Especially since NT feels it needs to
force files into a first letter capitalized scheme for some ungodly reason.
Another option would be to support translation tables for file names.
Basically a flat text file or DB that contains a lookup table of filename and
options like permissions( over and above the OSs ), case mode, etc. It would
just be a database that other mods could use to get data that we often wish we
had but don't. Such a table would go along way to simplifying the way we
identify SSIs and would fully enable security of servants on a URL or even USER
basis as was discussed in another post. I realize this mod would be no small
undertaking. But hey, neither was Apache. :-)
Just an idea.
Ron Burton
Steve Luzzi wrote:
> I manage a large website on a Solaris (case sensitive) platform
> and have never felt that the small percentage of errors showing up
> in the error_log regarding this have hurt our business.
>
> Steve Luzzi
> USACERL
> [EMAIL PROTECTED]
>
> >
> > At 07:26 PM 2/17/99 -0800, you wrote:
> > >
> > > I just built Apache v1.3.4 and JServ v1.b3 and it works fine but
> > >I can only have my servlets named in lowercase. Does anyone
> > >else have this issue?
> >
> > I brought up the issue of case sensitivity on a different list and was
> > slammed for being a terrible programmer. My point was that the servlet name
> > and the parameters are case sensitive. If a user uses the wrong case for
> > the servlet name, they can not access your site. If you are running a
> > commerical site, you are losing business. If the user uses the wrong case
> > for a parameter, you have to do extra coding to check for the parameter.
> >
> > I dropped the issue when one responder likened case insensitivity code to
> > the fall of man-kind despite I was explicitly not refering to code.
> >
> >
> >
> > ----------------------------------------------------------------
> > To subscribe: [EMAIL PROTECTED]
> > To unsubscribe: [EMAIL PROTECTED]
> > Archives and Other: <http://www.working-dogs.com/>
> > Problems?: [EMAIL PROTECTED]
> >
>
> ----------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://www.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
----------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://www.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
