Re: [newbie] Case Sensativity on web pages

2002-01-15 Thread Randy Kramer

Gerald Waugh wrote:
> If you take a look at the apache mod_speling (not a typo!) module, you can
> configure your server to do that (so I have heard)
> http://www.apache.org/docs/mod/mod_speling.html

Gerald,

Thanks -- I should have read this before I sent my last post!

Randy Kramer



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [newbie] Case Sensativity on web pages

2002-01-15 Thread Randy Kramer

I'm afraid I may have misled you with my reply -- I should not have
inplied that Apache can convert a mixed case file name to all upper or
lower, I really meant to speak hypothetically -- if something else
converted the file name to all upper or lower case (or if something was
built into Apache to do this), this would be an appropriate user
friendly approach.

I don't know that Apache, in its present incarnation, can do anything
along these lines.  (But, I don't know that it can't, either.)

Sorry for not being more clear,
Randy Kramer

Dragon . wrote:
> 
> Its a pretty simple web page, and converting everything to lowercase would
> be fine.  How many people do you know specifiy different file names on a web
> site by capitalization?  Personally, I don't know any.  I just wanted to
> make sure that people can see the site even if they have a problem typing
> uppercase and lowercase when they think it is proper.  Its really just a
> Directory test but you know some people love to type Test, and that doesn't
> work.  Thanks for the info.  I'll scrounge around apache's site a little
> more.
> 
> From: Randy Kramer <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: [newbie] Case Sensativity on web pages
> Date: Tue, 15 Jan 2002 07:17:45 -0500
> 
> Dave Sherman wrote:
>  > If you wanted to do that, you would be asking Apache to ignore the basic
>  > *nix filesystem rules, which I don't think is possible. The server would
>  > have to calculate every possible upper/lower case combination for each
>  > directory and file a user might request, and that would cause a
>  > (probably big) performance hit!
> 
> Just for the sake of completeness: Or, it could do what Windows does,
> basically convert the entire name to lower (or upper) case, i.e., it
> makes no distinction between, for example, TeSt and test.  I think there
> may be places where this is the appropriate user friendly behavior.
> 
>  > And if there are two files with the same
>  > name (except for upper/lower case), then what would Apache do?
> 
> If TeSt and test are indeed different files, Apache has a problem, if
> TeSt, test, TEST, etc. all refer to a file named test, Apache could
> handle it.  Of course, we would have fewer file names available.
> 
> Randy Kramer
> 
> Want to buy your Pack or Services from MandrakeSoft?
> Go to http://www.mandrakestore.com
> 
> _
> Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.
> 
> ---
> Want to buy your Pack or Services from MandrakeSoft?
> Go to http://www.mandrakestore.com



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [newbie] Case Sensativity on web pages

2002-01-15 Thread Gerald Waugh

On Tue, 15 Jan 2002, Randy Kramer wrote:
> >%_Dave Sherman wrote:
> > If you wanted to do that, you would be asking Apache to ignore the basic
> > *nix filesystem rules, which I don't think is possible. The server would
> > have to calculate every possible upper/lower case combination for each
> > directory and file a user might request, and that would cause a
> > (probably big) performance hit! 
> 
> Just for the sake of completeness: Or, it could do what Windows does,
> basically convert the entire name to lower (or upper) case, i.e., it
> makes no distinction between, for example, TeSt and test.  I think there
> may be places where this is the appropriate user friendly behavior.
> 
> > And if there are two files with the same
> > name (except for upper/lower case), then what would Apache do?
> 
> If TeSt and test are indeed different files, Apache has a problem, if
> TeSt, test, TEST, etc. all refer to a file named test, Apache could
> handle it.  Of course, we would have fewer file names available.

If you take a look at the apache mod_speling (not a typo!) module, you can
configure your server to do that (so I have heard)
http://www.apache.org/docs/mod/mod_speling.html

--
Gerald Waugh
Registered Linux User 255245
register at http://counter.li.org



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [newbie] Case Sensativity on web pages

2002-01-15 Thread Dragon .

Its a pretty simple web page, and converting everything to lowercase would 
be fine.  How many people do you know specifiy different file names on a web 
site by capitalization?  Personally, I don't know any.  I just wanted to 
make sure that people can see the site even if they have a problem typing 
uppercase and lowercase when they think it is proper.  Its really just a 
Directory test but you know some people love to type Test, and that doesn't 
work.  Thanks for the info.  I'll scrounge around apache's site a little 
more.

From: Randy Kramer <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [newbie] Case Sensativity on web pages
Date: Tue, 15 Jan 2002 07:17:45 -0500

Dave Sherman wrote:
 > If you wanted to do that, you would be asking Apache to ignore the basic
 > *nix filesystem rules, which I don't think is possible. The server would
 > have to calculate every possible upper/lower case combination for each
 > directory and file a user might request, and that would cause a
 > (probably big) performance hit!

Just for the sake of completeness: Or, it could do what Windows does,
basically convert the entire name to lower (or upper) case, i.e., it
makes no distinction between, for example, TeSt and test.  I think there
may be places where this is the appropriate user friendly behavior.

 > And if there are two files with the same
 > name (except for upper/lower case), then what would Apache do?

If TeSt and test are indeed different files, Apache has a problem, if
TeSt, test, TEST, etc. all refer to a file named test, Apache could
handle it.  Of course, we would have fewer file names available.

Randy Kramer

Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com


_
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.




Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [newbie] Case Sensativity on web pages

2002-01-15 Thread Randy Kramer

Dave Sherman wrote:
> If you wanted to do that, you would be asking Apache to ignore the basic
> *nix filesystem rules, which I don't think is possible. The server would
> have to calculate every possible upper/lower case combination for each
> directory and file a user might request, and that would cause a
> (probably big) performance hit! 

Just for the sake of completeness: Or, it could do what Windows does,
basically convert the entire name to lower (or upper) case, i.e., it
makes no distinction between, for example, TeSt and test.  I think there
may be places where this is the appropriate user friendly behavior.

> And if there are two files with the same
> name (except for upper/lower case), then what would Apache do?

If TeSt and test are indeed different files, Apache has a problem, if
TeSt, test, TEST, etc. all refer to a file named test, Apache could
handle it.  Of course, we would have fewer file names available.

Randy Kramer



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com



Re: [newbie] Case Sensativity on web pages

2002-01-14 Thread Dave Sherman

On Mon, 2002-01-14 at 21:37, Dragon . wrote:
> I was wondering if there was a way to take off the case sensativity for the 
> httpd.  I want to be able to browse to http:///test and 
> http:///TeSt for the same directory.  Currently, 
> http:///TeSt doesn't work but http:///test does.
> 
> --Dragon

If you wanted to do that, you would be asking Apache to ignore the basic
*nix filesystem rules, which I don't think is possible. The server would
have to calculate every possible upper/lower case combination for each
directory and file a user might request, and that would cause a
(probably big) performance hit! And if there are two files with the same
name (except for upper/lower case), then what would Apache do?

Dave
-- 
Do not meddle in the affairs of dragons, for you are crunchy, and good
with ketchup.




Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com