cURL / Mailing Lists / curl-library / Single Mail

curl-library

Re: Problems dealing with Authorization in RTSP

From: Tello Oraa <tello.oraa_at_sumenor.com>
Date: Thu, 5 Aug 2010 08:49:21 +0200

Date: Wed, 4 Aug 2010 13:37:10 -0400
From: Christopher Conroy <cconroy_at_gmail.com>
To: libcurl development <curl-library_at_cool.haxx.se>
Subject: Re: Problems dealing with Authorization in RTSP
Message-ID:
        <AANLkTinWyOg0hS8NJafUzDSS1+zL-LM+Vf23zgSQKCmd_at_mail.gmail.com>
Content-Type: text/plain; charset=windows-1252

On Wed, Aug 4, 2010 at 7:54 AM, Tello Oraa <tello.oraa_at_sumenor.com> wrote:
> Hi, I?m writing a RTSP client and I can?t find out how to provide
> authorization when sending a Describe message. I?ve tried setting
> CURLOPT_USERPWD but I have only succeeded with HTTP requests and not with
> RTSP requests. And so, I?m stuck with 401 Unauthorized responses (see the
> output #1 below).
>
>
>
> I have also tried by 64base encoding myself the user and password and
adding
> a custom header with that like this:
>
> Authorization: Basic ty6vdTy2dmlwc3VtXW
>
> This way I don?t get a 401 error, but a 200 OK what should be good, but
then
> the program gets stuck (output #2 below)
>
>
>
> Any comment regarding this issue would be highly appreciated.
>
>
>
> Regards,
>
>
>
> [Output #1]
>
>
>
> * About to connect() to 192.168.0.65 port 554 (#0)
>
> *?? Trying 192.168.0.65... * connected
>
> * Connected to 192.168.0.65 (192.168.0.65) port 554 (#0)
>
>> OPTIONS rtsp://myserver/path?videocdc=h.264 RTSP/1.0
>
> CSeq: 1
>
>
>
> < RTSP/1.0 200 OK
>
> < CSeq: 1
>
> < Public: DESCRIBE, GET_PARAMETER, PAUSE, PLAY, SETUP, SET_PARAMETER,
> TEARDOWN
>
> < Date: Wed, 04 Aug 2010 11:31:18 GMT
>
> <
>
> * Connection #0 to host 192.168.0.65 left intact
>
>
>
> * Re-using existing connection! (#0) with host 192.168.0.65
>
> * Connected to 192.168.0.65 (192.168.0.65) port 554 (#0)
>
>> DESCRIBE rtsp://myserver/path?videocdc=h.264 RTSP/1.0
>
> CSeq: 2
>
> Accept: application/sdp
>
> If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT
>
>
>
>
> < RTSP/1.0 401 Unauthorized
>
> < CSeq: 2
>
> < WWW-Authenticate: Digest realm="ISIS_00408CA15D41",
> nonce="0006b693Y085741c912e53c60710b9427535338f3a73d1", stale=FALSE
>
> < WWW-Authenticate: Basic realm="ISIS_00408CA15D41"
>
>
>
>
>
> [OUTPUT #2]
>
>
>
> (?)
>
>
>
> * Re-using existing connection! (#0) with host 192.168.0.65
>
> * Connected to 192.168.0.65 (192.168.0.65) port 554 (#0)
>
>> DESCRIBE rtsp://myserver/path?videocdc=h.264 RTSP/1.0
>
> CSeq: 2
>
> Accept: application/sdp
>
> If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT
>
>
>
>
> < RTSP/1.0 200 OK
>
> < CSeq: 2
>
> < Date: Wed, 04 Aug 2010 11:30:13 GMT
>
> <
>
> ? --- Gets stuck here

It doesn't work because it's not implemented yet.

from rtsp.c:
/*
 * TODO (general)
 * -incoming server requests
 * -server CSeq counter
 * -digest authentication
 * -connect thru proxy
 * -pipelining?
 */

-- 
OK, I didn't see that in the TODO list on the website, maybe it could be
good idea to add it?
I'll try to implement at least digest authentication and share it if it
works, any idea about where should I start ?
AVISO LEGAL
La Informacion incluida en el presente correo electronico es SECRETO PROFESIONAL Y CONFIDENCIAL, siendo para el uso exclusivo del destinatario arriba mencionado. Si usted lee este mensaje y no es el destinatario seƱalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicacion por error, le informamos que esta totalmente prohibida cualquier divulgacion, distribucion o reproduccion de esta comunicacion, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la direccion arriba mencionada. Gracias.
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html
Received on 2010-08-05