On Oct 31, 2004, at 4:39 PM, Mark Stosberg wrote:
Authentication to protect specific portions of the app. Can Basic
Authentication be used with C::A?
Sure.
You can use .htaccess and .htpasswd files if you want.
If your instance were in:
/cgi-bin/public
/cgi-bin/power
/cgi-bin/admin
You coud use
checking
the docs on how header_type works everytime (I have a short memory ;)
Thanks Cees, that works great.
Thank you to all who responded. I only wish that I had asked earlier.
You are all very helpful.
Ed Pigg
-
Web Archive: http
with mod_perl. For that matter, I don't work frequently
with Perl and C::A, so I've been coming back up to speed.
On 2/6/06 2:51 PM, Ed Pigg [EMAIL PROTECTED] wrote:
Hi all,
I'm reworking a C::A site to provide more flexibility and control.
This site has been functioning using Apache Basic
On Feb 6, 2006, at 1:51 PM, Ed Pigg wrote:
I may be missing something but I have not seen a mod_auth_mysql
module for apache.
As it turns out, there IS a mod_auth_mysql module for apache. Anyone
used it?
Ed Pigg
On Feb 20, 2006, at 6:51 PM, Ed Pigg wrote:
package MyApp;
use DBI;
use base 'CGI::Application';
use CGI::Application::Plugin::Session;
use CGI::Application::Plugin::DBH (qw/dbh_config dbh/);
use CGI::Application::Plugin::Authentication;
__PACKAGE__-authen-config(
# DRIVER = [ 'DBI
On Feb 21, 2006, at 9:48 AM, Cees Hek wrote:
On 2/21/06, Ed Pigg [EMAIL PROTECTED] wrote:
On Feb 20, 2006, at 6:51 PM, Ed Pigg wrote:
package MyApp;
use DBI;
use base 'CGI::Application';
use CGI::Application::Plugin::Session;
use CGI::Application::Plugin::DBH (qw/dbh_config dbh/);
use CGI
display_user_form edit_user /);
... module specific init items here
}
sub display_users {...}
sub display_user_form {...}
sub edit_user {...}
1;
Am I understanding the layout correctly?
Ed Pigg
-
Web Archive: http
On Apr 24, 2006, at 12:56 PM, Michael Peters wrote:
Cees Hek wrote:
On 4/24/06, Ed Pigg [EMAIL PROTECTED] wrote:
So how I put things like session initialization, database
connection,
etc.. in the SUPER::cgiapp_init sub. So my SUB CLASS would be
something like
sub cgiapp_init {
my
been to create a login module that my base app and Apache::AuthCookie.
package MyApp::Login;
use base qw( MyApp::Base Apache::AuthCookie );
Is this wise or prudent? Is there a better way to do this? I am open
to suggestions.
Ed Pigg
,
-path = '/', },
SEND_COOKIE = 1,
);
}
Thanks
Ed Pigg
-
Web Archive: http://www.mail-archive.com/cgiapp@lists.erlbaum.net/
http
').
At what point is this call made? In the Session options? Before
the session_config or after?
I do it just before session_config, so that the ensuing
CGI::Session object knows about it.
Thanks Rhesa. Works great.
Ed Pigg
common_function {
}
package myapp::somestuff;
use strict;
use warnings;
use base 'myapp::Base';
my somestuff_function {
my $self = shift;
my $value = $self-common_function();- error
common_function not found
}
Shouldn't all of the base class functions be inherited?
Ed Pigg
On Apr 29, 2006, at 2:28 PM, Ed Pigg wrote:
Changes to the derived package adding
use base 'myapp::Base';
__PACKAGE__-authen-protected_runmodes(':all');
.
added the login run_mode from the base class and now I am getting
the login run_mode when attempting to access the derived class
If I want to replace the built-in login form I need a method that
will generate the html form correct? So in my base class do I create
sub login_box {
}
?
or do I create a separate login sub.
Ed Pigg
-
Web
with the -T option of the instance scripts and need to untaint
the the environment variables. Is there a best practice for this?
Ed Pigg
-
Web Archive: http://www.mail-archive.com/cgiapp@lists.erlbaum.net/
http
On May 23, 2006, at 8:39 PM, Cees Hek wrote:
On 4/29/06, Ed Pigg [EMAIL PROTECTED] wrote:
If I want to replace the built-in login form I need a method that
will generate the html form correct? So in my base class do I create
sub login_box {
}
or do I create a separate login sub.
Looks
16 matches
Mail list logo
