HTTP Access and URLs

If deny/allow access control is present, only qualified clients are able to access the HTTP service as described in this chapter (see Access Control).

Accessing the Entry Page

The entry page is available at the “root” URL over HTTP just like this:

http://<address>:<port>/

Example:

http://172.17.2.100:8080

The trailing slash is usually added silently by the browser (if missing).

If the client accessing the entry page is restricted by the restrict/extend ACLs (see Access Control) this entry page doesn’t include the operational parameters and the virtual log terminal.

Getting a JPG-Picture (just take a Snapshot)

A current JPG-picture is available at this URL:

http://<address>:<port>/picture.jpg

Example:

http://172.17.2.100:8080/picture.jpg

Accessing the MJPG Stream

This URL accesses the MJPG stream with the default frame rate of 10 frames per second (FPS):

http://<address>:<port>/stream.mjpg

If desired, the client can specify the FPS frame rate which it wishes to receive like this:

http://<address>:<port>/stream.mjpg?fps=<frame-rate>

Examples:

http://172.17.2.100:8080/stream.mjpg
http://172.17.2.100:8080/stream.mjpg?fps=2

If the client accessing the entry page is restricted by the restrict/extend ACLs (see Access Control) the maximum frame rate for restricted clients is in effect - if specified with the -m option.

Accessing the virtual Log Terminal

Inlab-MJPG-Streamer comes with a virtual log terminal presented as a MJPG stream. This log terminal displays in parallel all syslog messages in real time in a 1024x768 text window. The syslog importance levels are visualised with the corresponding color.

This MJPG stream of the virtual log terminal is available like this:

http://<address>:<port>/log.mjpg

If the client accessing the entry page is restricted by the restrict/extend ACLs (see Access Control) this URL is not available and a 404 “not found” HTTP response is returned instead.

Example (A typical log terminal MJPG stream just after start looks like this (just with a blinking red cursor to visualise activity):

http://172.17.2.100:8080/log.mjpg

typical virtual log terminal after start

Changes with the -u Option

When Inlab-MJPG-Streamer has been started with the -u option specifying a “secreat URL component” all URLs need to include this component, otherwise a 404 not found is returned.

Example:

Let’s assume Inlab-MJPG-Streamer has been started like this:

$ streamer -uMySecretUrlComponent -b

then the above examples need to include this component as follows:

http://172.17.2.100:8080/MySecretUrlComponent/
http://172.17.2.100:8080/MySecretUrlComponent/picture.jpg
http://172.17.2.100:8080/MySecretUrlComponent/stream.mjpg
http://172.17.2.100:8080/MySecretUrlComponent/stream.mjpg?fps=2
http://172.17.2.100:8080/MySecretUrlComponent/log.mjpg