Check out REST Webservices and CGI.pm ... CGI should be handling PUT and POST (and DELETE and GET) correctly. Can you provide code examples? As for PROPFIND ... meh ... I would vote against polluting CGI with support for it (but that's not my call). As for not having an account to submit bugs, come on it takes about 30 second to create a bitcard account.

-derby

Update: Okay missed the link to REST Webservices and CGI.pm (it was more work to write it up than actually create a patch) ... code please ... and failing test cases.

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

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.