curlopt_rtsp_stream_uri(3) [mojave man page]

CURLOPT_RTSP_STREAM_URI(3)				     curl_easy_setopt options					CURLOPT_RTSP_STREAM_URI(3)

NAME

       CURLOPT_RTSP_STREAM_URI - set RTSP stream URI

SYNOPSIS

       #include <curl/curl.h>

       CURLcode curl_easy_setopt(CURL *handle, CURLOPT_RTSP_STREAM_URI, char *URI);

DESCRIPTION

       Set  the  stream  URI  to  operate  on  by passing a char * . For example, a single session may be controlling rtsp://foo/twister/audio and
       rtsp://foo/twister/video and the application can switch to the appropriate stream using this option. If	unset,	libcurl  will  default	to
       operating  on  generic server options by passing '*' in the place of the RTSP Stream URI. This option is distinct from CURLOPT_URL(3). When
       working with RTSP, the CURLOPT_RTSP_STREAM_URI(3) indicates what URL to send to the server in the request header while  the  CURLOPT_URL(3)
       indicates where to make the connection to.  (e.g. the CURLOPT_URL(3) for the above examples might be set to rtsp://foo/twister

       The application does not have to keep the string around after setting this option.

DEFAULT

PROTOCOLS

       RTSP

EXAMPLE

       TODO

AVAILABILITY

       Added in 7.20.0

RETURN VALUE

       Returns CURLE_OK if the option is supported, CURLE_UNKNOWN_OPTION if not, or CURLE_OUT_OF_MEMORY if there was insufficient heap space.

SEE ALSO

       CURLOPT_RTSP_REQUEST(3), CURLOPT_RTSP_TRANSPORT(3),

libcurl 7.54.0							 December 21, 2016					CURLOPT_RTSP_STREAM_URI(3)

CURLOPT_RANGE(3)					     curl_easy_setopt options						  CURLOPT_RANGE(3)

NAME

       CURLOPT_RANGE - set byte range to request

SYNOPSIS

       #include <curl/curl.h>

       CURLcode curl_easy_setopt(CURL *handle, CURLOPT_RANGE, char *range);

DESCRIPTION

       Pass a char * as parameter, which should contain the specified range you want to retrieve. It should be in the format "X-Y", where either X
       or Y may be left out and X and Y are byte indexes.

       HTTP transfers also support several intervals, separated with commas as in "X-Y,N-M". Using this kind of multiple intervals will cause  the
       HTTP server to send the response document in pieces (using standard MIME separation techniques). Unfortunately, the HTTP standard (RFC 7233
       section 3.1) allows servers to ignore range requests so even when you set CURLOPT_RANGE(3) for a request, you may end up getting  the  full
       response sent back.

       For RTSP, the formatting of a range should follow RFC2326 Section 12.29. For RTSP, byte ranges are not permitted. Instead, ranges should be
       given in npt, utc, or smpte formats.

       Pass a NULL to this option to disable the use of ranges.

       The application does not have to keep the string around after setting this option.

DEFAULT

       NULL

PROTOCOLS

       HTTP, FTP, FILE, RTSP and SFTP.

EXAMPLE

       CURL *curl = curl_easy_init();
       if(curl) {
	 curl_easy_setopt(curl, CURLOPT_URL, "http://example.com");

	 /* get the first 200 bytes */
	 curl_easy_setopt(curl, CURLOPT_RANGE, "0-199");

	 /* Perform the request */
	 curl_easy_perform(curl);
       }

AVAILABILITY

       FILE since 7.18.0, RTSP since 7.20.0

RETURN VALUE

       Returns CURLE_OK on success or CURLE_OUT_OF_MEMORY if there was insufficient heap space.

SEE ALSO

       CURLOPT_RESUME_FROM(3),

libcurl 7.54.0							 December 21, 2016						  CURLOPT_RANGE(3)