My first question is will a reverse proxy effectively allow me to host a website on the same network as the Blue Iris server and make it look like the Blue Iris camera feeds are in a subdirectory of the website?
Secondly, is it possible to set an htaccess or NGINX rule (in the case of a Linux web server) that will, in effect, intercept connection attempts to anything within the subdirectory used to view Blue Iris camera feeds?
Currently, I have an htaccess rule that says, "If trying to access anything within a certain directory, in this case /wp-content/uploads/, instead load a PHP file, which checks to see if the traffic or connection meets certain conditions, in this case is logged into the site as a user in the WordPress database. But would this actually work with a Blue Iris camera feed that originates from the same place, accomplished presumably through a reverse proxy, when it is not technically a file?
Ultimately, I am trying to design a solution that replaces an old system where Blue Iris (version 3, if you can believe it) outputs one JPEG file per second into a directory, and the public URL for that image is used to embed it on a protected page on a WordPress website. The issue is that copying and pasting the image URL means that it can be viewed by anybody with the link. Where I am at right now is putting the WordPress website on the same network or server as the Blue Iris server so that Blue Iris can output the images files directly to the website (WordPress directory) and thus use an htaccess rule to intercept and protect access to the automatically-refreshing JPEG files.
Secondly, is it possible to set an htaccess or NGINX rule (in the case of a Linux web server) that will, in effect, intercept connection attempts to anything within the subdirectory used to view Blue Iris camera feeds?
Currently, I have an htaccess rule that says, "If trying to access anything within a certain directory, in this case /wp-content/uploads/, instead load a PHP file, which checks to see if the traffic or connection meets certain conditions, in this case is logged into the site as a user in the WordPress database. But would this actually work with a Blue Iris camera feed that originates from the same place, accomplished presumably through a reverse proxy, when it is not technically a file?
Ultimately, I am trying to design a solution that replaces an old system where Blue Iris (version 3, if you can believe it) outputs one JPEG file per second into a directory, and the public URL for that image is used to embed it on a protected page on a WordPress website. The issue is that copying and pasting the image URL means that it can be viewed by anybody with the link. Where I am at right now is putting the WordPress website on the same network or server as the Blue Iris server so that Blue Iris can output the images files directly to the website (WordPress directory) and thus use an htaccess rule to intercept and protect access to the automatically-refreshing JPEG files.