Hi Dan,

On Thu, Dec 22, 2011, Dan Fandrich wrote:

> I think you're missing my first preference:
>
> 4) Break the commands into two categories: those that return a "body"
> and those that don't:
>
> Body-returning: LIST, UIDL, RETR, TOP, CAPA
> Non-body-returning: STAT, NOOP, DELE, RSET

It's been a while since we talked about this but I just want to say that I'm
taking another look at this and working on your suggestions as we speak.

There is also LIST <message id> which falls into the Non-body-returning
category so I guess the user would have to specify "LIST 10" in the custom
command, for example, as well as CURLOPT_NOBODY.

> I still like option 4), leaving it to the user to specify a sane set of
overrides.
> But, we'd still need a way to specify a URL that doesn't expect a body.
> Maybe just change POP3 so that if CURLOPT_NOBODY is set, it performs
> a STAT command and doesn't expect a body, and use that as the basis for
> overriding with the other non-body-returning commands. Also, the
> non-body-returning commands could be sent as quote commands.

Just one quick question...

Unless I've missed something (which is quite possible) what's curl.exe's
command line equivalent of CURLOPT_NOBODY?

Cheers

Steve

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2012-02-23