Just converting my software from wget to curl.

Just discovered a main advantage:

The handling when not 200 OK

I use --include
Veray similar is --save-header in wget

But there is a main difference.
When the server does not respond 200 OK

wget: 0 byte length file is saved
curl: the file is saved as usual

Twitter gives often a 403 forbidden
and explains the situation in the content.

For example try to follow
403 forbidden

You already followed USER_NAME

It's not possible to find this out with WGET,
0 byte saved, but now I can extract the
reason with curl

best regards

Roland Mösl
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ: http://curl.haxx.se/docs/faq.html
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2010-07-30