Setting up a secure connection to a legacy Axis camera
If the camera you are connecting to does not support the latest TLS (Transport Layer Security), you can configure one of four
HTTP headers, a Content-Security-Policy header, to provide a secure connection. The Content-Security-Policy HTTP response
header reduces XSS (Cross-site scripting) risks on modern browsers by declaring which dynamic resources are allowed to load.
Prerequisites: You are working in
- Double–click the station’s WebService ().The WebService Property Sheet opens.
- Expand .The system displays the Content-Security-Policy properties.
- Configure at least
connect-srcandmedia-srcand click Save.connect-srcdefines the hostname (IP address) of the camera(s). For example:'self' workbench ws://%hostname%:%port% wss://%hostname%:%port% ws://172.16.254.1 wss://*training.lan connects to all cameras on the training.lan (a network).'self' workbench ws://%hostname%:%port% wss://%hostname%:%port% ws://192.168.1.* wss://192.168.1.* includes any camera with an IP address that starts with 192.168.1 and uses either HTTP or HTTPS.
media-srcidentifies valid sources for loading media. Set this value to ‘self’ blob:.