I’ll take a look to see if I can work around that when a camera replies with null instead of a valid location. I can probably get it going but you will need to move all 3 controls to then get an accurate location from the camera so a rule on openhab startup to specify a XYZ location would be a good idea.
The illegal characters are in the header of the reply back from the camera. You could confirm this with the Linux tool ‘tcpdump’. The : in the request is not there, it is my way of showing where the url starts and stops in the logs so I can see if carriage returns and the like are entered in by users in the snapshot override field. The best way forward would be to use tcpdump to confirm if it is the camera or not so if it is a bug in the netty library we can report it. I think it will be the camera so check for a newer firmware.
Your camera is not giving a content length on how large the picture is and this is causing the issue. I may be able to work around this camera issue by guessing how much ram is needed but I would need to err on the larger side and it would place more ram requirements on your server. Maybe 500kb per picture I could guess at. At the least I will detect and put something in the logs that this is happening so thanks for the log.