An Enterprise feature, Web Panels allow you to monitor or interact with web pages from the internet or from local intranet sites.
Web Panels aid in keeping user attention to ExacqVision rather than needing to navigate to a separate browser.
Tag: Web
Affected platforms
exacqVision 7.2 or later
<br>
Description
exacqVision 7.2 introduces native h.264 video streaming to the web client. When a browser session connects to the web service, the browser and web service negotiate whether transcoding or native streaming will be used. The following logic describes how this is negotiated:
- If the browser does not support web sockets, fall back to polling (traditional method).
- This includes IE8 and 9.
- Since IE8 does not support the HTML5 element, it plays back by displaying the image element directly.
- If the user has disabled software decoding on the client configuration page, use web sockets JPEG.
- This method is similar to traditional polling, but the delivery mechanism causes frames to be sent as they are generated.
- If the camera is not native H.264, use web sockets JPEG.
- This includes digital PTZ “cameras” whose parent camera may be h.264, but as a virtual camera, they are not.
- If the camera’s resolution is 167% larger than the panel, use web sockets JPEG.
- There is very little gain in rendering native h.264 on small panels.
At this point, the camera will attempt native h.264 decoding. If it succeeds, it will play back using software decoding. Otherwise, it will fall back to web sockets JPEG.
Affected platforms
Web Service 7.2.0, 7.2.1
<br>
Symptom
In the 7.2.0 release candidate of web service, if the machine the web service is running on does not have access to Amazon Web Services (AWS) for push notifications, the web service will crash on start.
In the 7.2.1 release candidate of web service, if the machine the web service is running on does not have access to AWS for push notifications, the web service will block other HTTP requests to the web server while trying to reach AWS, rendering the web server unresponsive.
<br>
Workaround
If the machine does not have access to AWS (e.g. behind a corporate firewall with no Internet access) push notifications will not work and should be disabled. This ensures that the web service won’t crash or become unresponsive.
To disable push notifications:
- Login to the webservice configuration page service.web.
- Uncheck all of the power user process checkboxes (if any)
Leaving the power user processes enabled without internet access can cause the web service to not respond to any HTTP requests while it is busy trying to contact AWS services.
<br>
Resolution
No resolution available at this time.
Description
The version of Apache embedded in the web service has been found to expose a security vulnerability, known as “httpoxy” (technical details: CVE-2016-5387). This vulnerability can be avoided by changing the configuration of Apache.
<br>
Version Introduced
2.3.9
<br>
Platform
Web Service / All
<br>
Work Around
- Open the evApache httpd.conffile for editing
Windows: C:\Program Files\exacqVision\WebService\evApache\conf\httpd.conf
Linux: /etc/evapache/httpd.conf - Find and change the line #LoadModule headers_module modules/mod_headers.so to LoadModule headers_module modules/mod_headers.so. (Remove the ‘#’)
- Add the following line to the end of the file: RequestHeader unset Proxy early
- Save the file.
- Restart the web service.
Description
Most modern browsers provide a privacy mode for viewing web sites (e.g. “Incognito Mode” for Chrome, “Privacy Window” for Firefox, “InPrivate Window” for Edge). These privacy modes all operate on the same core principles, by not allowing any data generated by that browser window to persist once it is closed.
The web client stores a number of user settings in local storage (e.g. which servers are enabled, any stored credentials, user preferences) so that they are restored when the user revisits the page. When accessing the web client using a privacy mode, all of this generated data is cleared, and subsequent visits to the web client will not restore any of these settings.
<br>
Platform
Web Client / All
<br>
Steps to reproduce
- Access the web client in a browser’s privacy mode.
- Change some user settings (such as those in the Gears tab->Client page).
- Close the browser window.
- Revisit the web client in the browser’s privacy mode.
<br>
Expected result
The user settings are retained.
<br>
Actual result
No user settings are retained.
<br>
Work Around
There is no direct workaround, this is behaving exactly as these privacy modes are intended. To persist user data in the web client, do not use a privacy mode when accessing the site.
Description
In the web service, as the source resolution of a camera grows, the ability to quickly stream frames is reduced. This is particularly noticeable with cameras of 1080p resolution or higher. When this issue occurs, video will start displaying at extremely slow frame rates and, when switching to a larger layout, some video will not load at all.
<br>
Version Introduced
7.1.9
<br>
Platform
Web Service / All
<br>
Steps to reproduce
- Connect high resolution (1080p or greater) cameras to a server.
- View the cameras on the web service over web sockets.
<br>
Expected result
The cameras stream at roughly the same rate as legacy polling.
<br>
Actual result
The cameras stream at extremely low rates (<1FPS).
<br>
Work Around
Either:
- Prefer legacy polling in the web client.
- On the gears tab, select “Client”.
- Check the “Use Legacy Poll” checkbox.
- Refresh the page.
- Create lower resolution secondary streams and use those.
- Using the client, create a secondary stream with a lower resolution for each camera.
- Using the client, create a view containing each of these secondary streams.
- In the web client, prefer these secondary streams over the primary.
Updating exacqVision Web Server version via Web Service Configuration
- Open your web browser and navigate to your exacqVision web server.
<br>
NOTE: If accessing from the computer hosting the exacqVision web service, the default address is http://127.0.0.1. If exacqVision Web Server has been configured to use a custom port that port number must appended to the address (http://127.0.0.1:8080)You should now see the exacqVision Web Server landing page.
<br>
- You should now see the exacqVision Web Server landing page.
- Click on the “Web Service Configuration” hyperlink in the lower right-hand corner of the exacqVision Web Server landing page
<br>
- Enter your Web Service Configuration admin credentials when prompted.
<br>
- Click on Configuration to expand the Section.
- Click on Updates to bring up the Update Page.
- Click Check for Updates.
<br>
- If No updates are available you will see the following, click OK to return to configuration.
<br>
- If updates are available, the most recent will be displayed.
- Click on Install to launch the installer or cancel to cancel the update.
<br>
- You will be prompted to confirm the installation, click Yes to proceed.
<br>
- A series of screens will appear, showing the update is being downloaded and then installed.
<br>
- Once the install has completed you will be returned to the Web Service Configuration login screen.
- Enter your credentials or click the “Return to Landing Page” hyperlink in the upper right-hand corner.
<br>
Checking The Current Version
- The update can be verified in Web Service Configuration on the Service Info Page.
<br>
How-to-update-the-exacqVision-Web-Server.pdf