Re: httpd.conf's 407 setting doesn't quite work

2000-01-25 Thread Chuck O'Donnell 

How about

ErrorDocument 401 /error.html

Thanks,

Chuck

On Thu, Jan 20, 2000 at 12:39:23PM -0800, Nancy Lin wrote:
 
 Hi 
 
 I don't know if this is a problem w/ modperl or apache itself.
 
 I'm running proxy server apache 1.3.9 and modperl 1.21.  I'm using modperl
 to authenticate my users.  When a
 user is invalid, my code does:
 
   } else {
   loginfo($r, "AuthenSession::handler: bad password") ;
   $r-note_basic_auth_failure;
   return AUTH_REQUIRED;
   }
 
 On Netscape 3.x, a little window pops up saying authentication failed, do
 you want to retry?  Here's the part I don't quite understand.  If I
 configure httpd.conf with 'ErrorDocument 407 "Wrong Password!', that's
 what I'll see when I click on the Cancel button on that little popup.
 But, if I configure httpd.conf with 'ErrorDocument 407 /error.html, it
 gives me the default error 407 page.  I'm not sure why it's doing that.  I
 would rather point this to an file than to write it in httpd.conf.
 
 My httpd.conf has:
 
 Directory /opt/apache/http-proxy/htdocs
 Options Indexes FollowSymLinks ExecCGI
 AllowOverride None
 Order Allow,Deny
 Allow from All
 #require valid-user
 /Directory
 
 Directory proxy:*
 order deny,allow
 allow from all
 AuthName "Test"
 AuthType Basic
 PerlAuthenHandler Apache::AuthenSession
 require valid-user
 /Directory
 
 
 
 Thanks
 
 -- 
 Nancy

Re: httpd.conf's 407 setting doesn't quite work

2000-01-25 Thread Chuck O'Donnell 

On Fri, Jan 21, 2000 at 01:33:05PM -0800, Nancy Lin wrote:
 
 That worked!  But can you tell me why it worked?  
 
 Thanks

I think because you're using 401-type authentication below, both in
your httpd.conf and by returning AUTH_REQUIRED below which maps to a
401 error.

I'm not very familiar with proxy authentication, but I don't believe
mod_proxy supports "407 HTTP_PROXY_AUTHENTICATION_REQUIRED" yet. It
says it supports up to HTTP/1.0 in the docs, and 407 is an HTTP/1.1
status code as far as I know. Maybe someone else can help here with
better info.

Chuck


 
 -- 
 Nancy
 
 
 On Fri, 21 Jan 2000, Chuck O'Donnell wrote:
 
  How about
  
  ErrorDocument 401 /error.html
  
  Thanks,
  
  Chuck
  
  On Thu, Jan 20, 2000 at 12:39:23PM -0800, Nancy Lin wrote:
   
   Hi 
   
   I don't know if this is a problem w/ modperl or apache itself.
   
   I'm running proxy server apache 1.3.9 and modperl 1.21.  I'm using modperl
   to authenticate my users.  When a
   user is invalid, my code does:
   
 } else {
 loginfo($r, "AuthenSession::handler: bad password") ;
 $r-note_basic_auth_failure;
 return AUTH_REQUIRED;
 }
   
   On Netscape 3.x, a little window pops up saying authentication failed, do
   you want to retry?  Here's the part I don't quite understand.  If I
   configure httpd.conf with 'ErrorDocument 407 "Wrong Password!', that's
   what I'll see when I click on the Cancel button on that little popup.
   But, if I configure httpd.conf with 'ErrorDocument 407 /error.html, it
   gives me the default error 407 page.  I'm not sure why it's doing that.  I
   would rather point this to an file than to write it in httpd.conf.
   
   My httpd.conf has:
   
   Directory /opt/apache/http-proxy/htdocs
   Options Indexes FollowSymLinks ExecCGI
   AllowOverride None
   Order Allow,Deny
   Allow from All
   #require valid-user
   /Directory
   
   Directory proxy:*
   order deny,allow
   allow from all
   AuthName "Test"
   AuthType Basic
   PerlAuthenHandler Apache::AuthenSession
   require valid-user
   /Directory
   
   
   
   Thanks
   
   -- 
   Nancy

Re: Content management system

1999-12-02 Thread Chuck O'Donnell 

On Thu, Dec 02, 1999 at 09:08:19PM +, Matt Sergeant wrote:
 On Thu, 02 Dec 1999, Chuck O'Donnell wrote:
  On Wed, Dec 01, 1999 at 04:05:06PM +0400, BeerBong wrote:
   Hello all!
   
   Are there any freeware content management systems kinda Zope or simpler on
   Perl ?
   What do you can recommend ?
   Where I can search for its ?
  
  Mason has one http://www.masonhq.com
 
 Mason is (IIRC) a component based development system - not a content
 management system. Think of a system that automatically takes care of
 object management, versioning, a test and live server, an admin front end
 (be it web based or not) and you've got a content management system. Throw
 in something like mason for developing components and you've got something
 really interesting for non-hardcore developers. They're not for everyone,
 but in certain cases they can make life easier.

I guess I should have been more specific... I think the Mason guys
have created a fairly nice content management system built on top of
the Mason component framework. The following is taken from the Mason
site (http://www.masonhq.com/Mason-CM/)

---

  We are proud to announce the initial public release of the Mason
  Content Management system. Content Management makes it easy to
  navigate the content of a website and manage the workflow of
  information as it moves from staging to the live, production web
  site.
  
  Content Management features: 
  
  * Easily navigate multiple filesystems: create, copy, rename and edit
files and directories
  * Search for files based on file name or contents 
  * Trigger (copy) files between staging and production sites
  * Track changes between staging and production, save versions (via
Rcs)
  * Edit files on staging, with an integrated, HTML-friendly
spell-checker
  * File locking protects multiple users from editing the same file
  * Control access to directories on a per-user basis
  
  We'll be putting up a demo of Content Management soon here on
  MasonHQ, but in the meantime, download a copy and let me know what
  you think. You can also have a look at the user manual.

---

I haven't used the content management system, but we've been using
Mason for quite a while, and find it to be a very stable and usable
application framework.

Thanks,

Chuck