X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: <75cc17ac0709130748v14989cc9m41c859c1d7b24aff@mail.gmail.com> Date: Thu, 13 Sep 2007 09:48:26 -0500 From: "Gregg Reynolds" To: cygwin@cygwin.com Subject: Re: Webdav batch file transfer: curl, wget In-Reply-To: <46E82389.28C5B4D9@dessent.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <75cc17ac0709111359u1b7635ej4cc3bab19658af46@mail.gmail.com> <46E82389.28C5B4D9@dessent.net> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 9/12/07, Brian Dessent wrote: > Curl on the other hand is better suited for http scripting where you are > trying to emulate the actions of a user, such as when submitting form > fields. Wget has the ability to do http POSTs but it only supports the > old "application/x-www-form-urlencoded" content encoding and not the > more sophisticated "multipart/form-data" encoding which allows for > things like file uploads. Curl supports both. Curl is also great for examining protocol transactions for any of the supported protocols. Great tool for e.g. learning what webdav transactions actually look like. I wouldn't want to try to debug a networking application without it, that's for sure. -g -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/