CURLOPT_POST deserved a new comment with the new POST-by-callback support

1 files changed, 3 insertions, 2 deletions

diff --git a/lib/url.c b/lib/url.c
index cd1854328..a75fafbc4 100644
--- a/lib/url.c
+++ b/lib/url.c
@@ -634,8 +634,9 @@ CURLcode Curl_setopt(struct SessionHandle *data, CURLoption option, ...)
     data->set.use_port = va_arg(param, long);
     break;
   case CURLOPT_POST:
-    /* Does this option serve a purpose anymore? */
-
+    /* Does this option serve a purpose anymore? Yes it does, when
+       CURLOPT_POSTFIELDS isn't used and the POST data is read off the
+       callback! */
     if(va_arg(param, long))
       data->set.httpreq = HTTPREQ_POST;
     break;