Re: [cgiapp] CGI::Application::Plugin::Authentication

(Olivier Salaun's package). c -- Nicholas Bamber | http://www.periapt.co.uk/ PGP key 3BFFE73C from pgp.mit.edu # CGI::Application community mailing list #### ## To unsubscribe, or change your message delivery

[cgiapp] Syntax error in CGI::Application::Dispatch

/ Sent from my iPhone -- ___ cgiapp mailing list cgiapp@lists.erlbaum.net http://www.erlbaum.net/mailman/listinfo/cgiapp End of cgiapp Digest, Vol 48, Issue 1 * -- Nicholas Bamber

Re: [cgiapp] CGI::Session

On 07/07/11 01:45, Ron Savage wrote: Hi Nick On Wed, 2011-07-06 at 14:35 +0100, Nicholas Bamber wrote: Ron, You put an explicit version on every dependency. For example Data::Dumper 2.128. That seems unnecessarily modern and Debian curently only has 2.125. If we added the latest

[cgiapp] CGI::Session

The latest release of CGI::Session appears to be unauthorized. I can find it at http://search.cpan.org/~markstos/CGI-Session-4.45/ but ifyou click on permalink it disappears. # CGI::Application community mailing list ##

Re: [cgiapp] cgiapp Digest, Vol 45, Issue 11

/mailman/listinfo/cgiapp End of cgiapp Digest, Vol 45, Issue 11 ** -- Nicholas Bamber | http://www.periapt.co.uk/ PGP key 3BFFE73C from pgp.mit.edu # CGI::Application community mailing list

[cgiapp] Data::session

: 1293169066.3514.29.ca...@localhost.localdomain Content-Type: text/plain Hi Nicholas On Sat, 2010-12-18 at 23:37 +, Nicholas Bamber wrote: I notice that a 4.43 o CGI::Session has been released. That should get into Debian in due course. Reviewing the Debian bug list I noticed

[cgiapp] Data::Session/CGI::Session

I notice that a 4.43 o CGI::Session has been released. That should get into Debian in due course. Reviewing the Debian bug list I noticed this: Session file not being written for driver:File; serializer:Storable (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=315669) That appears to be

Re: [cgiapp] : CGI::Session

Ron/Jason, Actually, anything and everything which give people information (on which to base decisions pertaining to their own lives) helps. Thanks for the information. This exactly describes my problem. Mark refuses to release until I make changes he insists on. The ostensible

[cgiapp] CGI::Session

Ron, There's no point - Mark Stosberg refuses to release any more versions of CGI::Session. http://github.com/cromedome/cgi-session/blob/master/Changes This looks like an abortive attempt to restart development. Are you saying that Mark is trying to prevent further development, or is to

[cgiapp] Data validation of file uploads

There are two Data::FormValidator related modules that handle file uploads. They both take the approach of saying, Well the CGI module param method (or equivalent) gives us a file handle. So whatever we do with the file handle or the underlying file, there must still be a file handle at the

Re: [cgiapp] Unobtrusive Javascript form validation

The company I work for has also been moving to JQuery, so I won't be surprised if Data.FormValidator gets updated at some point to integrate better with JQuery, possibly on a fork. This is a frustrating thing about javascript. I use YUI. I have very poor experience from

Re: [cgiapp] Problems with uploads

Hi Nicholas / A lot of my troubles seem to have come from following the HTML, XHTML, / / and CSS Bible by Steven Shafer which recomends a form like this: / / / / form action=formhandler.cgi method=post enctype=form/multipart // // input type=file id=file size=10/ .. // / / I was slightly

[cgiapp] Problems with uploads

I have just had a terrible time getting file uploads to work with CGI::Application. I ended up working with a hacked version of CGI.pm that was writing statements to a local file. I have had to temporarily abandon test-driven development in favour of just get the damn thing working - sort of -

[cgiapp] authentication stuff

Jerry, I hate to say this, but I cannot help thinking you would benefit from stepping back from the problem. Start off with a basic CGIApp, add authentication, the add the DBH plugin, then switch to the DBI based driver then go back to your code. Even if that does not reveal the problem the

Re: [cgiapp] cgiapp Digest, Vol 33, Issue 16

Jerry, Just focusing on this for a moment: Error executing class callback in prerun stage: must call dbh_config() before calling dbh(). What this seems to mean is that $options{DBH} is undefined. I assume you have had CGI::Application working with the standard DBH authentication driver. I am

[cgiapp] Using HTTP chunked transfer with CGI::App?

Hi Des, I would suggest that you look into AJAX and try to handle rather more on the client/javascript side. If you will permit I will give some hints on how I would approach it. There are alternatives but I primarily use the YUI framework for javascript stuff. 1.) The CGI::Application part

[cgiapp] Multiple Authentications?

Jerry, The answer to your title question is yes - you can have multiple DBI drivers. There is an example in the main documentation where there are two Generic drivers and that should carry across. However I don't think this will quite do what you want. First of all the authentication module

Re: [cgiapp] Incompatibility between CAP::Authentication and CAP::ActionDispatch

I've uploaded 0.17_5 which has the ActionDispatch fix and hopefully should run fine without ActionDispatch being installed. The question Christian raises about Dispatch is interesting. As Christian points out I am not a fan of setting up run modes by setting subroutine attributes. I can see

[cgiapp] Security, Authentication and Authorization for CGI::App

Brad, If you have any feedback on CGI::Application::Plugin::Authentication I would appreciate it. My priorities for it are (not in any order): 1.) Getting it to run under taint mode 2.) And making the HTML more configurable 3.) Getting test coverage up. 4.) Keeping test failures down