Interval snapshot - working examples for web page

[rheine3]

If you have your own webpage and don't want slow loading problems and jerky vids try snapshots. I can monitor all my cams with snaps and click through to one with streaming video if I see a problem. This also prevents a lock on concurrent user access.

IPV6 - snapshot every 5 seconds. This is for a IP2M-842B but the onload= will work for all camera that can snapshot.

<img src="http://NAME:PWD@[IPV6 use the brackets too]:PORT/cgi-bin/snapshot.cgi?t=" onload='setTimeout(function() {src = src.substring(0, (src.lastIndexOf("t=")+2))+(new Date()).getTime()}, 5000)' onerror='setTimeout(function() {src = src.substring(0, (src.lastIndexOf("t=")+2))+(new Date()).getTime()}, 5000)' alt='TEXT' height="240" width="320"/>

IPV4 - snapshot every 5 seconds. This is for a IP2M-842B

<img src="http://NAME:PASSWORD@IPADDRESS:PORT/cgi-bin/snapshot.cgi?t=" onload='setTimeout(function() {src = src.substring(0, (src.lastIndexOf("t=")+2))+(new Date()).getTime()}, 5000)' onerror='setTimeout(function() {src = src.substring(0, (src.lastIndexOf("t=")+2))+(new Date()).getTime()}, 5000)' alt='TEXT' height="240" width="320"/>

IPV4 - snapshot every 5 seconds. This is for a FOSCAM F18918W

<img src="http://IPADDRESS:PORT/snapshot.cgi?user=NAME&pwd=PASSWORD&t=" onload='setTimeout(function() {src = src.substring(0, (src.lastIndexOf("t=")+2))+(new Date()).getTime()}, 5000)' onerror='setTimeout(function() {src = src.substring(0, (src.lastIndexOf("t=")+2))+(new Date()).getTime()}, 5000)' alt='TEXT' height="240" width="320" />

[TheUberOverLord]

I am the original author of the methods you show here:

http://foscam.us/forum/a-how-to-embed-a ... t9113.html

That said.

There are a few major issues with my methods, for displaying IP Camera(s) in a public web page on a website.

1. My methods are not secure for public web pages on websites and exposed everything about the IP Camera including IP Address and/or DDNS, Port and User credentials.

This invites abuse of your camera. Which can include logging into that IP camera reaching enough concurrent logons to lock you the owner of the IP Camera from being able to login to your own IP Camera(s).

Additionally, this also allows others to create multiple video streams to your cameras potentially exceeding any monthly ISP bandwidth limitations one may have at the IP Cameras location. Potentially causing that ISP service to be suspended for the remainder of the month or cause additional charges for that month.

2. Not all browsers support using the "Basic Authorization" methods ("http://User:Password@DDNS:Port") including IE ("Internet Explorer") browsers. This means that not all your website visitors could see your IP Camera(s).

3. Some Internet connections don't support accessing non-standard ports ("Ports other than 80 and 443") such as corporate proxies and free Internet connections. So people using those Internet connections would not be able to see your IP Camera if say your IP Camera Port was 4000.

Here are secure methods that work with all Internet browser capable devices from Computers to Tablets and Phones to TV's that do work that also include live demonstrations using Amcrest IP Cameras. Since the Interface acts as a proxy there are no port number issues as well:

https://amcrest.com/forum/general-discu ... html#p5198

Don

[rheine3]

I ordered the popular $9.95 package through PayPal of all the code to do a secure setup. Never heard from them.

That's where I am at. I can lock down my webpage.

[TheUberOverLord]

I ordered the popular $9.95 package through PayPal of all the code to do a secure setup. Never heard from them.

That's where I am at. I can lock down my webpage.

There are instructions that need to be followed when ordering.

More here: http://107.170.59.150/paypal/

When the instructions are not followed then you need to send your transaction information for your order to the Email address shown at the above link. So that I can manually send you the .zip file via Email.

My methods you show here are/were never intended to be used in public websites. Locking down your webpage won't make my methods more secure for a public website. Which is why I responded here warning others of that fact. While also providing newer secure methods that do work with public websites.

Don