# HTTP Bindings for Axis camera **URL:** \ **Category:** Ignition\ **Tags:** ignition81, perspective, scripting\ **Created:** [September 20, 2024, 8:01pm UTC](https://forum.inductiveautomation.com/t/http-bindings-for-axis-camera/96256 "2024-09-20T20:01:10Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [September 21, 2024, 12:07am UTC](https://forum.inductiveautomation.com/t/http-bindings-for-axis-camera/96256/4 "2024-09-21T00:07:57Z")
Whether video or audio or IFrames, such components need the URL supplied as a string, not a binding, because they make the connection they need on their own, from the **browser side**. For such purposes, Ignition simply does not support digest authentication. Sorry. You will need to transcode/proxy through another server. Perhaps the gateway itself, via my Image Streamer module (but beware of the CPU load that generates): > [@Automation Professionals' Image Streamer Driver Module](https://forum.inductiveautomation.com/t/automation-professionals-image-streamer-driver-module/29371): > > Automation Professionals is pleased to announce a Release Candidate for its new driver module, supporting the live Network Image transmission format of [Keyence CV-5000](https://www.keyence.com/products/vision/vision-sys/cv-5000/index.jsp) machine vision controllers, plus support for common Network Video streams via [OpenCV](https://opencv.org/). Stream metadata is exposed as OPC items, and the output streams are Motion JPEG. The IP Camera Viewer Component in Vision can consume these streams, making it possible to integrate IP Cameras that don't have MJPEG support or have poor support f… --- _[View the full topic](https://forum.inductiveautomation.com/t/http-bindings-for-axis-camera/96256)._