News:

Added a Wiki, please help to add pages to the wiki! - http://wiki.openipcam.com

Author Topic: Secure Methods Using PHP To display Your IP Camera  (Read 15983 times)

  • ***
February 17, 2014, 10:36:52 am
Any IP Camera owner can optionally easily get and use All my many different IP Camera examples bundled together with one hour of one-on-one support to implement them. Save Time and Money Click Here!



One of the downsides of normally displaying a "Real-Time" image of your IP Camera in a Blog, Forum or Web Page. Is that you expose your IP Cameras DDNS and Port or ISP IP Address and Port and a User Id and Password credentials for your IP Camera.

Here are methods to display your IP Cameras in Web Pages. Blogs, Forums anyplace where you can include an image in your post. As well as your own web pages which can now include a "Real-Time" Snapshot image of your IP Camera. Without needing to display any IP Camera IP location or IP Camera User credentials. With or without your own custom text and/or date and time stamps embedded in the actual image displayed.



The above is a Real-Time Image of an IP Camera That has no IP Camera Information connected to it.
You can refresh this Forum web page to see it automatically update.


More details here:

http://foscam.us/forum/secure-methods-using-php-to-display-your-ip-camera-t8721.html#p42139

Don
« Last Edit: December 28, 2014, 09:15:10 am by TheUberOverLord »

  • ***
February 28, 2014, 01:39:48 pm
Any IP Camera owner can optionally easily get and use All my many different IP Camera examples bundled together with one hour of one-on-one support to implement them. Save Time and Money Click Here!

Unlike the misunderstood concept that by simply encrypting the HTML source code used to access the IP Camera. Could/Would by itself, protect the IP Cameras, DDNS, IP Address, Port, User Id and Password information from being exposed. Which is not true or correct.

You can use tools like ANY browser debugger included with ANY browser, Fiddler2 or Wireshark to confirm that no information of any kind is exposed about the IP Camera used in these first two secure examples shown here. The third example shown here is a non-secure example.

Fiddler2 was used here to demonstrate. What information a client device would have access to, about the IP Camera being accessed. When that client device is using HTTP and HTML on a client device to access a IP Camera. Using the secure and non-secure methods. With or without HTML encrypted source code. The results would be the same.

Here are also examples of using these methods for totally secure access to your IP Camera with automatically refreshing images by using the php code shown here inside HTML. That works using ANY Internet browser capable devices that are running on any Operating System which are using any browser:

http://107.170.59.150/SecureRefreshWithCustomText.htm

Note: The below is the servers IP Address when the above link is used. NOT the IP Cameras IP Address


Note: There is additional overhead involved in the above example due to modifying the images in real-time with custom text such as date and time.

Whereas leaving the image as it was received cuts down this overhead:

http://107.170.59.150/SecureRefreshWithoutText.htm

Note: The below is the servers IP Address when the above link is used. NOT the IP Cameras IP Address


The above examples. Have no linkage of any kind as to what the IP Cameras DDNS or IP Address, Port, User Id or Password is.

As stated earlier here. These secure examples are substantially much slower then using non-secure methods like the example below. Which also works with any Internet browser capable devices as well. Such as this:

http://107.170.59.150/GenericBIV31.htm

Note: The below IS the IP Cameras Address when the above link is used. Including DDNS, ISP IP Address, User Id and Password Information


Which would still be exposed even with encryption method concepts. When using HTTP and HTML alone from any client device.

This is why php was chosen for these methods. Because not all IP Cameras support HTTPS and even if they did. There are easy methods to get the same IP Camera information using tools like Fiddler2 on the client device side. Whereas by using php. This is not possible.

The results of all the two secure and one insecure methods shown here for IP Camera automatic refresh average turn around times for each image are:

Code: [Select]
Secure With Custom Text:    450 Milliseconds
Secure Without Custom Text: 250 Milliseconds
Unsecured:                   44 Milliseconds

Of course you can use these same secure or non-secure methods with single snapshots or automatic image refreshes using multiple IP Cameras on the same Web Page. That can be any mix of IP Camera Brands and Models and types such as MJPEG or H.264 based. One Example showing something like this. Using one IP Camera to represent multiple IP Cameras for live demonstration purposes. The live demo below is throttling each camera shown to a maximum of 1 FPS ("Frames Per Second") for live demonstration purposes:

http://www.saveontelephonebills.com/camera/EmbedWebPageExample.htm

Don
« Last Edit: December 28, 2014, 09:32:07 am by TheUberOverLord »

  • ***
February 28, 2014, 01:43:12 pm
Any IP Camera owner can optionally easily get and use All my many different IP Camera examples bundled together with one hour of one-on-one support to implement them. Save Time and Money Click Here!

While many of the members here run Linux 24/7 and I have dual boot systems that use Ubuntu from time to time but mainly use Windows based systems.

Even if you currently don't have a Web Server or Hosting Service to host php examples like this. It's easy to start doing so. For as little as $5 U.S. dollars a month. Using Hosting Services like as just one example DigitalOcean's Digital Cloud SSD ("Solid State Drive") VPS ("Virtual Private Servers") Hosting Services:

Click for Info

Note: If anyone needs help setting something up like this. Please ask here. This was a first for me as well doing something like this from scratch. In the past I have used Shared Hosting Services to do run my Web Sites. But, there just are too many resource restrictions in place and I wanted something to be running Linux 24/7 which I can use for all my IP Cameras. That I also had full control of.

Which I used specifically for the examples in my prior post here. As to not be subjected to any resource restrictions by a Shared Hosting Service. Which I used for my other examples here in the original post and also use normally as well. Also there is no need to any need to use or register any Domain name to do this. Also saving money.

Where you can configure your own flavor of Linux systems and options. To do things like this and also store other data from your IP Cameras. Like your own FTP interface without being subjected to any restrictions a Shared Hosting Service may have. Such as blocked ports, memory usage, process usage and other limits they may impose.

These are the Web Server resources being used with one copy of each example above being run at the same time


Above Web Server was configured for these example with:

Ubuntu 12.04.3 x64 1GB Ram 30GB SSD Disk 2TB Transfer per Month Bandwidth Maximum
Apache/2.2.22 (Ubuntu)
PHP/5.3.10-1ubuntu3.9 with Suhosin-Patch Click to see options
Varnish
MySQL
memcache
swap file
FFmpeg
avconv

The beauty about going this route, for IP Camera owners who don't normally run Linux as their default Operating System. Is that you can control every aspect of what software you use for your Web Server as well as stop/start the Web Server as needed to make changes. The IP Address is unique and can be used directly without any Domain name if needed. As the example here is doing.

The Web Server is your personal Web Server. Without being shared by others. So you have a clear view of the resource being used and also knowing that all those resources are your resources. So that you can do Web Server Tuning as well. It can also support as many Domains as you wish. In the event your currently have Web Sites and are under restrictions on a Shared Hosting Plan.

It's a great alternative method to store Snapshots and Videos for your IP Cameras, without the need to run your own system to do so 24/7/365. It also has built-in RAID ("Redundant Array of Independent Disks") so even a disk outage would not cause a loss of IP Camera files. After all the purpose of IP Cameras are security. So, having fault-tolerant disk storage is important. Even more so for multiple IP Cameras.

I also wanted to set the stage for my next posts here. Which will be about providing secure real-time video using a video server ("Which most likely Shared Hosting Services would not allow") from your IP Cameras and generating SMS messages, when your IP Cameras detect alarms or go offline or become unavailable.

While many IP Cameras have the ability to tell you when their ISP IP Address changes. None have the ability to tell you that they went offline and are not currently available.

Don
« Last Edit: December 28, 2014, 09:32:27 am by TheUberOverLord »

  • ***
March 03, 2014, 08:53:41 pm
Any IP Camera owner can optionally easily get and use All my many different IP Camera examples bundled together with one hour of one-on-one support to implement them. Save Time and Money Click Here!

A new version 2.0 was released:

Changes;

1. Now supports using Curl methods when the image is pulled from the IP Camera and no custom text is used and no disk recovery is used.

2. Includes example HTML that uses the php code for automatic image refreshes based on a timeout value in Milliseconds which you configure.

Please see this for the new version:

http://foscam.us/forum/secure-methods-using-php-to-display-your-ip-camera-t8721.html#p42139

This allows the same php code too support as many methods as possible including being very fast but also being totally secure.

So that no information about your IP Camera is exposed of any kind. Such as DDNS, ISP IP Address, Port, User Id or Password. While displaying your IP Camera publicly on or in a webpage.

Two examples:

1. Using a Snapshot in a Forum, Blog, Email or on a Web page in your post. Everyone who sees that post. Will see a current image of your IP Camera:



The above was done by simply using the IMG tag in the post here:

Code: [Select]
[img]http://107.170.59.150/ipcamera.php[/img]

2. Embedding your IP Camera in a Web Page or as a link in Web pages, Emails and Chats. With images that automatically refresh at the interval of your choice:

http://107.170.59.150/SecureRefreshWithCustomText.htm

Note: For demonstration purposes. The resolution in the above examples is set to 160x120.

These methods can also be used when for example you are using a public WiFi interface with whatever device you have currently and you don't wish to expose any of your IP Camera information. But you want to use that device to see your camera in real-time using a single Snapshot or automatically refreshed Snapshot images.

Otherwise. You run the risk if you are using an Admin User level Id for your IP camera with a public connection of exposing your IP Cameras information where someone could obtain Email and FTP server user and password information. If that information is stored in the IP Cameras configuration. When you use a unsecure connection.

Don
« Last Edit: December 28, 2014, 09:32:44 am by TheUberOverLord »

  • ***
March 14, 2014, 06:27:23 pm
Any IP Camera owner can optionally easily get and use All my many different IP Camera examples bundled together with one hour of one-on-one support to implement them. Save Time and Money Click Here!

New version released and more live demonstrations. This Interface and all of its features, works with ANY IP Camera Brand and Model and any imaging device that can provide Snapshots via HTTP and/or HTTPS:

Free SecureImageDisplay Version 4.2

Image sizes for the examples shown here are small for demonstration purposes. You can use any sizes.

This Interface works with ALL Foscam IP Camera models and virtually all other IP Cameras as well as any imaging devices that can supply Snapshots via HTTP and/or HTTPS and is compatible with any and all Internet browser capable devices running on any Operating System and using any browser. From Computers to Tablets to Phones and TVs.

Here are the current options this Interface supports:

Display Custom Logos and images in your IP Cameras Images
Instantly Works With Any/All Internet Browser Capable Devices
Totally Secure With or Without Controls and With or Without HTTPS
Always Totally Secure Using Any Internet Connection
Securely Post Real-Time Camera Images Anywhere Even Emails
Securely Display As Many Cameras As Needed At Same Time
For Emergency Use When Stuck Using Other Devices
Works Behind Corporate And Other Proxies
Require Unique User and Password to Access
Allows HTTPS Access Even For MJPEG Based IP Cameras
Set Time Limit for Viewing
Use Any Size Automatically Refreshed Images Clickable or Not
Use Automatically Refreshed Thumbnails Clickable or Not
Use Any Size Static But Real-Time Images Clickable or Not
Use Real-Time Images in Social Media Websites, Forums and Blogs
Extended Access Restrictions for ALL Foscam IP Camera Models
Save Last Real-Time Image From Foscam IP Camera To Disk
Real-Time Image Request Throttling 
Auto-Recovery Display Last Image Saved When Camera Is Offline
Automatic Image Percentage Resize
Automatic Image Fixed Size Resize
Insert Date Time and Custom Text Into Images
Time Zone Offset When Web Server Is In Another Time Zone
Controlled Privacy Display Last Image Saved During Private Times
Automatic Image Refreshing Using HTML Front-End ("Example Included")

Click on any of the Fourteen Foscam U.S. Demo IP Camera images below to view a specific IP Camera in real-time using unsecure methods. If the IP Camera or imaging device in question natively supports HTTPS then even the unsecure Interfaces can be changed to use HTTPS vs. HTTP and be secure as well.

Last Real-Time Images Stored On Disk Displayed - CDT Time


Live Demonstrations Using Secure Methods For ALL Foscam U.S. Demo IP Cameras:

Without Login Required:

http://107.170.59.150/foscam/FoscamUS.htm

User Name and Password can be ANY combination of characters. Please note that when using HTTP the User and Password are sent in the clear in this Login example. User name is admin Password is admin

With Login Required:

http://107.170.59.150/foscam/SecureImageDisplayLoginUS.php

The same can be done using HTTPS however the example is using a self-signed certificate so you will see a warning:

Without Login Required:

https://107.170.59.150/foscam/FoscamUS.htm

With Login Required:

https://107.170.59.150/foscam/SecureImageDisplayLoginUS.php

Extended Access Restrictions for all Foscam IP Camera Models

If someone were to try to access the Interface that was not allowed to do so and they tried to grab Snapshots or Refreshed Snapshots from your Foscam IP Camera(s). There are Extended Access Restrictions you can implement and use with the Interface. To deny anyone access to the Interface directly. Even if they know the file location of the Interface on the web server.

Example ("Compare above links HTML source code to links below"):

http://107.170.59.150/foscam/FoscamUSAttempt.htm

https://107.170.59.150/foscam/FoscamUSAttempt.htm

Click on any of the Six Foscam.com Demo IP Camera images below to view a specific IP Camera in real-time using unsecure methods. If the IP Camera or imaging device in question natively supports HTTPS then even the unsecure Interfaces can be changed to use HTTPS vs. HTTP and be secure as well.

Last Real-Time Images Stored On Disk Displayed - China Time

Live Demonstrations Using Secure Methods For ALL Foscam.com Demo IP Cameras:

Without Login Required:

http://107.170.59.150/foscam/FoscamChina.htm

User Name and Password can be ANY combination of characters. Please note that when using HTTP the User and Password are sent in the clear in this Login example. User name is admin Password is admin

With Login Required:

http://107.170.59.150/foscam/SecureImageDisplayLoginChina.php

The same can be done using HTTPS however the example is using a self-signed certificate so you will see a warning:

Without Login Required:

https://107.170.59.150/foscam/FoscamChina.htm

With Login Required:

https://107.170.59.150/foscam/SecureImageDisplayLoginChina.php

Extended Access Restrictions for all Foscam IP Camera Models

If someone were to try to access the Interface that was not allowed to do so and they tried to grab Snapshots or Refreshed Snapshots from your Foscam IP Camera(s). There are Extended Access Restrictions you can implement and use with the Interface. To deny anyone access to the Interface directly. Even if they know the file location of the Interface on the web server.

Example ("Compare above links HTML source code to links below"):

http://107.170.59.150/foscam/FoscamChinaAttempt.htm

https://107.170.59.150/foscam/FoscamChinaAttempt.htm

The Facts

One of the downsides of accessing your IP Cameras over insecure Internet connections or displaying "Real-Time" image(s) of your Foscam IP Cameras in Social Media sites, Blogs, Forums, Web Pages, Instant Messengers or even in Emails as an image or as links. Is that by doing so, you expose and show your Foscam IP Cameras DDNS and Port or ISP IP Address and Port and User Id and Password credentials for your Foscam IP Camera.

This Interface provides methods that resolve the above issues with future versions and functionality to come. Even while using HTTP unsecure access methods to any of your Foscam IP Cameras.

Secure Private Use

These images and their very secure methods. Contain no reference to your Foscam IP Cameras Model information, DDNS, IP Address or Cameras User credentials on where the Foscam IP Camera images originated from or how they were obtained.

In fact. These methods can be used to check on your Foscam IP Cameras when you are using any Internet browser capable device that is using public or semi-private Internet access. Such as public WiFi access or even your workplace and other semi-private internet connections for your Internet connection at that time.

Where you do not trust or wish to broadcast ANY information about your Foscam IP Cameras when accessing them on any risky or potentially unsecure Internet connection.

Where by doing so. Could and can expose you to Identity Theft or other IP Camera abuses. If others could use that exposed information. To abuse your IP Cameras by changing their position and/or viewing their video streams at anytime and/or gain access to your IP Cameras configurations. Thereby and possibly ("Depending on the User Id Level you used to access your IP Camera when using those unsecure Internet connections") others could also learn your Email and/or FTP User Ids and Passwords for them. Why take that RISK on a unsecure internet connection when there no longer is a need to do so?

Note: Once someone learns where your IP Camera is located ("DDNS and/or ISP IP Address") over an unsecure Internet connection. While also having any valid IP Camera User Id and Password information that was exposed because of using that unsecure Internet connection. They can connect to your IP Camera and based on the IP Cameras User Id level and Password that they ("Sniffed") and captured over a unsecured Internet connection. They can also determine what type of IP Camera is being used during that ("Sniffing") process.

At the very minimum, they would have unfettered 24/7/365 access to your IP Cameras video streams anytime your IP Camera was online and still using that same DDNS and Port or ISP IP Address and Port and User Id and Password for that IP Camera, that they ("Sniffed") on that unsecure Internet connection. That's a "Best Case" scenario and definitely not the worse case scenario and for sure, not worth the risk.

Some corporate, workplace, Hotspots and other Internet connections or their proxies. May block and not allow access to ports other than ports 80 and 443. This gets around those blocks as well. Allowing you to always have access to your Foscam IP Cameras.

Secure Public Use
 
Here are methods to securely display your Foscam IP Cameras "Real-Time"  in Social Media sites, Emails, Forums, Blogs, Web Pages, Instant Messengers and anyplace where you can include an image or links in your post. As well as your own web pages which can now include a "Real-Time" Snapshot image of your Foscam IP Camera.

Without needing to include or expose any reference to your Foscam IP Cameras DDNS, IP Address or Foscam IP Cameras User credentials. With or without your own custom text and/or date and timestamp embedded in the actual image(s) displayed.

This is an excellent method for example. To display a current single image or automatically refreshed images of any Foscam IP Camera. MJPEG or H.264 based, in Real-Time, on a web page at the time a visitor visits and views that webpage. Without giving up any information about your Foscam IP Camera location or user credentials. While and when doing so.

Download

Both these examples require having access to a Web Server with PHP.

In some cases. Web Hosting services do NOT allow access to non-standard outgoing ports. Meaning a port other then port 80. If your Web Hosting service will not open a non-standard port to your current Foscam IP Cameras port. You will be forced to use port 80 for your Foscam IP Camera, to get this to work. The php script automatically checks and reports if this is the case.

The ten files required for this Interface. All in a .zip file can be downloaded here:

http://107.170.59.150/V40/SecureImageDisplayV40.zip

These examples below are using a 160x120 and 320x180 resolutions for live demonstration purposes. But you can display any camera resolution for your Real-Time Snapshots or automatic refreshed Snapshots of your Foscam IP Camera on Social Media sites, Blogs, Forums or anywhere that allows you to add an images and/or links to your post. Including your Emails.

Examples

Both examples below are using the same Interface with different configuration options.

First Example - Simple Proxy

The first example. Simply pulls a current image from your Foscam IP Camera in "Real Time" and displays it on the web page that references it. Left is Foscam FI8918W. Right is Foscam FI9821W-V2:



The images you see above. Are Real-Time images that were just created when you loaded and viewed this Forum post web page. Not old images from when this post was created and posted here in the forum.

You can do the same on any Forum, Blog, Social Media Site, Web Pages, Instant Messengers and in Emails that allows you to include images and/or links in your posts. Including your own Web Pages.

Even if the you are not allowed to include images in your posts. You can instead include a link that when clicked on can display a Real-Time image of your Foscam IP Camera. With or without custom text included in those images. Without exposing any information about your Foscam IP Cameras DDNS, ISP IP Address, Port, User Ids or Passwords to do so. Example:

Secure Single Images Without Custom Text

Foscam MJPEG based IP Camera:

http://107.170.59.150/FoscamPullImage2.php

Foscam H.264 based IP Camera:

http://107.170.59.150/test/SecureImageDisplayH264.php

You can also use these same secure methods that do not expose any information about your Foscam IP Camera. Such as your DDNS, ISP IP Address, Port, User Ids and Passwords. To display your Foscam IP Camera using automatic Real-Time images that refresh at the rate you desire by embedding the logic in a Web Page or including a link in Social Media sites, Blogs, Forums and Web Pages, Instant Messengers and your Emails. With or without custom text. Example:

Secure Images Automatically Refreshed Without Custom Text:

http://107.170.59.150/SecureRefreshWithoutText.htm

Display Multiple Cameras With Automatic Refreshed Secure Images

Images Automatically Refreshed With Multiple Cameras At The Same Time ("Same camera being used for live demonstration purposes"):

http://107.170.59.150/TwoCameras.htm

Note: You can display as many Foscam IP Cameras, at the same time as you wish. Each configured differently or the same. Each with or without custom text and using any combination of Foscam IP Camera models with each being the same or different sizes. In any display configuration you wish. With ALL Foscam IP Cameras being displayed. Using these totally secure methods.

The Web Server is not storing any image file on disk, in the above example.

This means that if your camera was offline or not available. That no images would be shown.

This example is simply acting as a go-between for where the images will be posted and the Foscam IP Camera. So that the location and User credentials for the Foscam IP Camera remain private and hidden.

Second Example - Custom Text - Automatic Throttle & Fallback

This example actually does create a single jpg file for each Foscam IP Camera on the web server, which is reused as needed. This can also help you control web server resources when using methods like this unlike example #1, which will try and pull a image, each and every time from your Foscam IP Camera.

This second example, has many benefits over the first example, shown here.

1. It stores the last real-time image received from your Foscam IP camera on disk ("With any changes you configured") so that IF your Foscam IP Camera was offline or not available. The last image stored on disk will be used automatically for image fallback and displayed automatically. Not letting anyone know your Foscam IP Camera is offline or not available. Assuming that your image is not using a timestamp of course.

2. You can set the number of seconds since the last real-time image received from your Foscam IP camera was written to disk to get a fresh image directly from your Foscam IP Camera. So that you can better control resources when/if needed. Only getting a fresh image from your Foscam IP Camera when or if the image on disk is greater then x seconds old. Automatically throttling real-time requests to your Foscam IP Camera.

3. Allows you to insert your custom text and/or a date timestamp into the actual image and store it on disk. Technically it's also possible to add your own logo to your Foscam IP Cameras images displayed, with few changes to do so.

4. Privacy. Say you don't want real-time images of your Foscam IP Camera displaying all the time. You can simply temporarily change the Password for the User Id that the Interface is using. In the Foscam IP Cameras configuration.

This will cause the Interfaces real-time request to the Foscam IP Camera when trying to get a real-time image to fail. Because the Interface will now be using the wrong Password.

With the Disk logging configuration on in the Interface. Then the last real-time image from your Foscam IP Camera will be used as the image displayed.

You then can at anytime later. Change the Password back to what the Interface is using and real-time images from your Foscam IP Camera will then be getting real-time images from your Foscam camera. Instead of the last image on disk.

Giving you privacy when you need it. While not displaying empty images while doing so.

5. You can access the last image stored on disk from the IP Camera directly.





The images you see above are "Real-Time" images that were created when you loaded and viewed this web page not old images from when this Forum post was created. They also create a single image file on the web server for each camera, that is reused and updated when this happens and that file can also be accessed directly as well.

Again, with no exposure of where the Foscam IP Cameras DDNS, or IP Address that created the image is located or any User Credentials for the Foscam IP Camera that produced the image above.

http://107.170.59.150/ipcam2.jpg

http://107.170.59.150/test/ipcam1.jpg

http://107.170.59.150/test/ipcam4.jpg

If any of the above Foscam IP Cameras were to go offline or become not available. Then the last real-time image received from the Foscam IP camera which was stored on disk. Would instead be used automatically and presented. Instead of a real-time image. This allows nobody to know that your Foscam IP Camera is offline or not available ("Assuming that you are not including date and time in your images").

Only the last real-time image received from your Foscam IP Camera is saved to disk, when using the disk option in the configuration for the Interface. So there is not any file clutter going on with multiple images from the same Foscam IP Camera being saved on disk.

Note: If you use the links above to get the files created by the images above, multiple times. Your browser may cache the files when using the link. Because the request to get the files, are not a unique request. However, the images shown above. Will be unique each and every time your refresh this Forum post web page, because it forces the images to be unique.

Both of these examples are TOTALLY secure methods. Simply using different configuration options available In the Interface. Allowing you to view your Foscam IP Cameras over unsecure Internet connections as well as share images of your Foscam IP Cameras. While providing total ambiguity about your Foscam IP Camera Model and maintaining the privacy of the DDNS, IP Address, Port and User Credentials of your Foscam IP Cameras.

You can create different copies of the Interface configured to be used for different purposes for the same Foscam IP Camera and you can use this Interface to display multiple Foscam IP Cameras at the same time. You can also reference and use any images created by the Interface that are stored on disk as the last image directly.

Secure Images and Refreshed Images Using HTTPS

Note: Even with the Foscam H.264 based IP Camera models that do support HTTPS. There is no requirement to port forward the HTTPS ports for those cameras to use these HTTPS methods with this Interface. Instead the Interface will use your SSL certificate on your Web Site avoiding any certificate warnings. If you have a valid and not self-signed SSL certificate for your Web Site.

The Interface also allows you to access any Foscam IP Camera model even MJPEG based camera models using HTTPS if desired. Accessing your Foscam MJPEG based IP Camera models, using HTTPS is normally not supported.

This can be very helpful if you wish to add your Foscam IP Camera in HTTPS based Web Pages.

Please note the Web Site being used for the examples is using a self-signed certificate which is why you will see a warning when using the example HTTPS links below:

Foscam MJPEG based IP Camera Single Secure Image:

https://107.170.59.150/ipcamera.php

Foscam H.264 based IP Camera Single Secure Image:

https://107.170.59.150/test/SecureImageDisplayH264WithText2.php

Two Foscam MJPEG based IP Cameras With Automatic Secure Image Refresh ("Same camera being used for live demonstration purposes:

https://107.170.59.150/TwoCameras.htm

Two Foscam H.264 based IP Cameras With Automatic Secure Image Refresh:

https://107.170.59.150/test/SecureImageDisplayH264Full2.htm

Secure Profile Pictures

In some cases, if your images are sized correctly. You can even use this Interface as your profile picture in Social Media sites, Blogs, Forums other Web Sites and even with some Instant Messengers. Allowing you to have Real-Time images of your Foscam IP Camera instead of any static images you currently maybe using there.

Unsecure Methods

These methods do not require having access to a web server. The actual HTML code can instead be stored on any browser capable device or even stored as an Email attachment and accessed from any browser capable device as needed.

Here are methods that will work with ANY IP Camera that will simply display refreshed images of your IP Cameras in a web page at your selected refresh rates and sizes. It only requires 1 line of HTML code per camera:

http://foscam.us/forum/a-how-to-embed-any-foscam-ip-camera-in-webpage-using-1-line-t9113.html#p43654

Here are unsecure methods to display and access your Foscam IP Cameras while using PTZ ("Pan/Tilt/Zoom") controls in a webpage as well:

MJPEG Based IP Cameras:

http://foscam.us/forum/post10970.html#p10970

H.264 Based IP Cameras:

http://foscam.us/forum/post20338.html#p20338

Don
« Last Edit: January 24, 2015, 05:58:28 pm by TheUberOverLord »

  • ***
July 13, 2015, 09:31:44 pm
Live demonstrations of using Hikvision Network IP Cameras in web pages on websites with PTZ ("Pan/Tilt/Zoom") and Preset controls. Which are compatible with any Internet browser capable devices using any Operating System and browser. No browser plugins or media players are required to ever be downloaded and/or installed at anytime.

New Hikvision live demonstrations using this Interface:



Time limits can also optionally be imposed to use a button to prompt to continue after a set period of viewing time of your Network IP Cameras has been reached and/or to jump to another web page on your website. To better help limit bandwidth usage and/or abuse.

Two live Hikvision examples with PTZ and Zoom lenses: Indoor Outdoor

Don
« Last Edit: July 17, 2015, 09:55:56 pm by TheUberOverLord »

  • ***
January 02, 2016, 07:51:16 am
This Interface can be used with any IP Camera/NVR/DVR/VMS that supports pulling snapshots using HTTP and/or HTTPS and is accessible from any Internet browser capable devices. From Computers to Tablets and Phones to TV's. That are using any Operating System and Browsers. Without downloading/installing any Plug-Ins or Media Players and IP Camera image refresh bandwidth can be controlled as well. Which makes it great for web pages in websites as well as for personal use from any of your Internet browser capable devices.

Examples:



Added live Axis IP Camera demos. Here's one that even allows you to start a train with all IP Camera controls:

http://107.170.59.150/Axis/SecureImageDisplayControl.htm

Another without IP Camera controls but with digital zoom:

http://107.170.59.150/Axis/SecureImageDisplayZoom1.htm

Another without any IP Camera controls and with a thermal image from the IP Camera above:

http://107.170.59.150/Axis/SecureImageDisplay2.htm

The Interface supports both HTTP and HTTPS and optionally prompting for access. Even if the IP Cameras does not support HTTPS. Unique User Id and Password that has nothing to do with the IP Cameras can also be used. The example below is using a self-signed certificate so you will see a warning. User: admin Password: admin

https://107.170.59.150/Axis/SecureImageDisplayControlLogin.php

Don
« Last Edit: January 02, 2016, 09:14:13 am by TheUberOverLord »

  • ***
June 15, 2016, 04:18:57 am
Created Version 5.

Download Link: http://107.170.59.150/V50/SecureImageDisplayV50.zip

Live Demos Using The Software: http://107.170.59.150

Enhancements:

1. Faster processing and less overhead.

2. Added digital zoom option.

3. Now supports Digest Authorization.

4. Images/Logos can now be embedded in the cameras image from a local file or from a website using HTTP and FTP.

5. When embedding images from weather sites. A delay can be used that stores the weather image in a local file and only gets a fresh copy when the weather website updates their image. Some weather websites update their weather images every 20 minutes. So this reduces logo/image processing and overhead. By storing the weather image locally and only making a remote request as needed.

Don

-Free IP Camera Software For Websites And Personal Use  -Live IP Camera Demos Using The Software  -About Me

 
« Last Edit: June 15, 2016, 04:29:09 am by TheUberOverLord »

  • ***
September 05, 2016, 07:49:31 am


Live example of Amcrest IP Camera using automatic refreshed snapshots and Digital Zoom. Totally secure without exposing any IP Camera information. No DDNS, ISP IP Address, Port or User Credentials are ever exposed and is compatible with all Internet capable devices using any browsers from Computers to Tablets to Phones and TV's. Without ever needing to install or download any plugins or media players:

http://107.170.59.150/Amcrest/SecureImageDisplayZoom.htm

Example of live Amcrest IP Camera with camera controls. Including PTZ, camera zoom and digital zoom:

http://107.170.59.150/Amcrest/SecureImageDisplayControl.htm

You can also choose your own unique User Id and Password as well:

User:admin Password:admin

http://107.170.59.150/Amcrest/SecureImageDisplayControlLogin.php

Note: You can use HTTPS as well. The test server running these live demos is using a self-signed certificate so it's normal to see a warning. Which you would not see with a proper HTTPS certificate :

https://107.170.59.150/Amcrest/SecureImageDisplayControl.htm

https://107.170.59.150/Amcrest/SecureImageDisplayControlLogin.php

Don