Re^3: Are all .cgi helper modules unfit for http methods common in REST?

If you're getting keyword set when processing a PUT request than your code (or HTTP::Request) is setting the content-type of the request to either multipart/form-data or application/x-www-form-urlencoded. You should set the content-type to something else (maybe text/xml).

-derby

Comment on Re^3: Are all .cgi helper modules unfit for http methods common in REST?

Replies are listed 'Best First'.
Re^4: Are all .cgi helper modules unfit for http methods common in REST? by isync (Hermit) on Aug 13, 2010 at 09:49 UTC
That makes sense. So my requests were faulty.. 1:0 for CGI.pm	[reply]
Re^4: Are all .cgi helper modules unfit for http methods common in REST? by isync (Hermit) on Aug 13, 2010 at 18:55 UTC
Tested this with my test-client.pl script here, and as you said, doing PUTs with a proper header does lead to CGI.pm parsing out PUTPARAM. (As a sidenote, what will CGI.pm parse out on other methods like PROPFIND? PROPFINDDATA??) Problem is, if you intend to use this all here for WebDAV, you can't control the clients behaving nicely. For example, gvfs, GNOME's DAV client - as I see it - does not set any headers on requests... Read more... (4 kB)	[reply] [d/l]
Re^5: Are all .cgi helper modules unfit for http methods common in REST? by Anonymous Monk on Aug 13, 2010 at 19:37 UTC
As a sidenote, what will CGI.pm parse out on other methods like PROPFIND? PROPFINDDATA??) Should be easy to find out :p	[reply]