[Live-devel] RTSP-over-HTTP question

Kamil Dobkowski kamildobk at poczta.onet.pl
Fri Oct 22 02:05:29 PDT 2010


Hi,

Below is wireshark output of 'openRTSP.exe -T 80 -u admin admin -F 
rtp_data -m rtsp://192.168.3.4/VideoInput/1/h264/1'


GET /VideoInput/1/h264/1 HTTP/1.0
CSeq: 1
User-Agent: openRTSP.exe (LIVE555 Streaming Media v2010.10.20)
x-sessioncookie: 4d4566946d3c5c4b79a2fd3
Accept: application/x-rtsp-tunnelled
Pragma: no-cache
Cache-Control: no-cache

HTTP/1.0 401 Unauthorized
WWW-Authenticate: Basic realm="You need ID"



<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
"http://www.w3.org/TR/html4/loose.dtd">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META HTTP-EQUIV="Content-Script-Type" CONTENT="text/javascript">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
<TITLE>SANYO NETWORK CAMERA</TITLE>
<SCRIPT language="JavaScript">

<!--
//-->

</SCRIPT>
<STYLE TYPE="text/css">
<!--
BODY {color:#ffffff; font-family:Arial, sans-serif; font-size:12pt; 
font-weight:bold; background-color:#000000; }
.top {font-family:Arial, sans-serif; font-size:20pt; font-weight:bold; }
.content {font-family:Arial, sans-serif; font-size:12pt; font-weight:bold; }
-->

</STYLE></HEAD><BODY><CENTER><TABLE BORDER="0"><TR><TD ALIGN="CENTER" 
CLASS="top">AUTHENTICATION 
ERROR</TD></TR><TR><TD><BR></TD></TR><TR><TD><BR></TD></TR><TR><TD 
ALIGN="CENTER" CLASS="content">Please input a correct user 
name/password</TD></TR></TABLE><BR></CENTER></BODY></HTML>

GET /VideoInput/1/h264/1 HTTP/1.0
CSeq: 3
Authorization: Basic YWRtaW46YWRtaW4=
User-Agent: openRTSP.exe (LIVE555 Streaming Media v2010.10.20)
x-sessioncookie: dbe115cec3266617fab9b26
Accept: application/x-rtsp-tunnelled
Pragma: no-cache
Cache-Control: no-cache



and that's all ... I see no other requests sent to the server. I think the 
problem is beacause this server does not immediately close its connection 
after http reply, so client is able to send a repeated request during the 
same connection but it is ignored by the server. When I turn off client 
authorization everything goes ok.

Regards,
Kamil




More information about the live-devel mailing list