Multi-User Security on *nix using mod_rewrite

This WebDNA talk-list message is from

2002


It keeps the original formatting.
numero = 41716
interpreted = N
texte = After reading through the docs on mod_rewrite I believe that it could be used to secure, on a directory or host basis, the usage of the WebDNA Engine based on file extension. This could be a great way to provide standard hosting on the same machine as WebDNA if it really could be made to work. I haven't yet started in on it because I wanted to know if anyone has already tried it. If so, does it work. If not, why not. It seems, as it runs off of regular expression, that explicit denial of any registered extension processed by WebDNA could be rewritten to an error page or the like and that this denial could be either file path based or host header based or both.Any mod_rewrite gurus out there that want to comment?Mike ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Multi-User Security on *nix using mod_rewrite (Alain Russell 2002)
  2. Re: Multi-User Security on *nix using mod_rewrite (Aaron Lynch 2002)
  3. Re: Multi-User Security on *nix using mod_rewrite (Aaron Lynch 2002)
  4. Re: Multi-User Security on *nix using mod_rewrite (Clement Ross 2002)
  5. Re: Multi-User Security on *nix using mod_rewrite (Alain Russell 2002)
  6. Multi-User Security on *nix using mod_rewrite (Michael Davis 2002)
After reading through the docs on mod_rewrite I believe that it could be used to secure, on a directory or host basis, the usage of the WebDNA Engine based on file extension. This could be a great way to provide standard hosting on the same machine as WebDNA if it really could be made to work. I haven't yet started in on it because I wanted to know if anyone has already tried it. If so, does it work. If not, why not. It seems, as it runs off of regular expression, that explicit denial of any registered extension processed by WebDNA could be rewritten to an error page or the like and that this denial could be either file path based or host header based or both.Any mod_rewrite gurus out there that want to comment?Mike ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Michael Davis

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

OBDC Support (1997) remotely add + sign (1997) Re:Emailer and encryption (1997) [WebDNA] [then] statement not showing (2012) Summary layout (1997) RE: [WebDNA] html email.. should be a no-brainer.. but it is not parsing. (?) (2010) cybercash (2002) Search returns all, not 20 (1997) a search based on ^(contains) (1998) Aaron kant add (or whatever it was) (2000) Server Freeze (1998) searching multiple databases (1997) Next X hits (1996) Search Command, multiple dbs, etc. --Getting Results Now! (2000) Can he do that? (1998) Feature: TCPconnect via SSL (1999) Re:no [search] with NT (1997) [WebDNA] Finding duplicate records (2011) Getting total number of items ordered (1997) WebCatalog Install Problems (2000)