Hi, all:

Thank you for your attention once again. I thought password should be set
after transcode to base64, but a 401 response. Later I removed the base64
transcoding section, it works ok. Maybe libcurl have transcoded somthing I
don't know.

Best Regards!

2014-03-14 2:24 GMT+08:00 <jeremy_at_fastmail.co.uk>:

> On Wed, Mar 12, 2014, at 10:12, zy wu wrote:
> > I compiled the libcurl with that patch , but it seems little effect,
> prompt "401
> > Unauthorized". I captured the net packet and found the password is
> encrpted. Also I
> > followed jeremy's advice, is there anything else to do before set user
> and password?
>
> You could try replacing CURLAUTH_ANY with CURLAUTH_BASIC, that will make
> the password visible in your wireshark trace. I think you should see in
> your trace something like the RTSP options request sent, an initial 401
> response from the camera, the RTSP options resent then the 200 response
> (assuming the username and password are correct).
>
> > is there anything else to do before set user and password?
> No, just make sure they are set before doing the curl_easy_perform of
> the CURL_RTSPREQ_OPTIONS. Also,
> my_curl_easy_setopt(curl, CURLOPT_HTTPAUTH, CURLAUTH_ANY);
> should probably read
> my_curl_easy_setopt(curl, CURLOPT_HTTPAUTH, (long)CURLAUTH_ANY);
>
> -------------------------------------------------------------------
> List admin: http://cool.haxx.se/list/listinfo/curl-library
> Etiquette: http://curl.haxx.se/mail/etiquette.html
>

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2014-03-14