On Fri, Dec 31, 2010 at 05:01:14PM +0100, Erlend Leganger wrote: > Heh, you learn something new every day... I configured my Apache > server and made a PUT handler as described in [1], then I can use curl > on the client to upload files: > curl --request PUT --upload-file heartbeat.txt > -Hheartbeatfile:$(hostname)-heartbeat.txt > http://localhost/cgi-bin/put-heartbeat.pl > The -Hheartbeatfile stuff is something I invented to pass a file name > to the CGI-script. > Now suddenly this became a solution that can be deployed across WAN > links and is as scalable as the target web server - nice!
That great, glad you found the suggestion useful. I will reach out and make one other suggestion. It looks like you used the legacy put cgi method. I don't think there is anything wrong with it, but I believe the more accepted method now is to just use webdav and limit everything except put. Of course you might be doing some extra fancy processing in your put.pl script which would probably not be able to be done with straight webdav. Anyway glad to see thats working out for you. Seems like a cool idea that i may have to use myself. _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
