Gary Littlemore wrote:
quavoce wrote:I'm in contact with him now so hopefully won't be long).
This is awesome, taking it to the next level
The IP Cam Pro developer replied with the following along with a bug report that I'm hoping you can look into please?
"ok, wait for the next update.
after the next update, the "RPi Cam Web Interface" camera type will auto-detect if form login is required so no new camera type is required.
now, I have a bug to report to you. it exists in the older versions and your 6.2.19 demo version as well.
If you use the "RPi Cam Web v6" camera type instead, the detail view's video will break up and connection is lost.
The detail view uses "/cam_pic_new.php" for mjpeg.
The reason is the that the mjpeg content-length returned by the rpi server is WRONG (too short).
Why does this happen on this driver? see below:
The "RPi Cam Web Interface" requests HTTP 1.0 so mjpeg content-length is correct.
The "RPi Cam Web v6" requests HTTP 1.1 but ***without*** content chunking.
The reason it works in browsers is because they accept content chunking.
So, I believe the mjpeg content-length is wrong when chunking is not accepted (because rpi server code assumes chunking somewhere)..."