in reply to Re: Are all .cgi helper modules unfit for http methods common in REST?
in thread Are all .cgi helper modules unfit for http methods common in REST?

Edited my post to include this node while you wrote your post...

You are right with bitcard, but who wants all these bug reports from a noob who is now banging his head against the wall for two days before finding out that these proven decade-old modules were the initial bug that caused endless rewrites, commenting in/out, design changes, etc.
My strategy is to hope that the (active) module maintainers follow discussion here anyway and they are best to decide if what I am observing is a bug, or simply incompetence.
  • Comment on Re^2: Are all .cgi helper modules unfit for http methods common in REST?

Replies are listed 'Best First'.
Re^3: Are all .cgi helper modules unfit for http methods common in REST?
by derby (Abbot) on Aug 12, 2010 at 20:32 UTC

    Gotcha. Okay ... I normally use bare-bones CGI::Application and do something like this:

    package MyApp; use base 'CGI::Application'; .... sub setup { my $self = shift; my $cgi = $self->query(); $self->start_mode( $cgi->request_method() ); $self->run_modes( 'PUT' => 'create', 'GET' => 'retrieve', 'POST' => 'update', 'DELETE' => 'delete', 'AUTOLOAD' => 'method_not_supported' ); return; } .... 1;
    I have no idea if PROPFIND would work or not (I'm pretty much WebDAV ignorant). I do believe you still have problems with marshalling (CGI will try to copy that 2G POST/PUT into a scalar and that will probably not go well.

    -derby