eldy
commented
8 years ago Your note is correct. However, i can't find any solution. If kb reported is full size of file and not real viewed size, bandwith report will be wrong. Solution should be to first find a way to setup apache to get the real viewed kb.
Hello We are using awstats for streaming logs, progresive download/pseudostreaming, both lighty and apache.
We are having some troubles with status code 103 that is returned by apache. If code 103 is included in awstats ValidHTTPCodes it will be seen as valid hit but every 103 code return as %b the entire video file size.
So it looks to me if someone click a few times on the video timeline to look ahead in the video each click is logged as code 103 with the entire video file size. So 5 clicks in the timeline equals as if the entire video is viewed 5 times, in terms of bandwidth. This ends up in exponential bandwidth consumption in the logs that didn't really happen.
I believe this happens only with httpd with h264_mod, the problem is not present with lighttpd with h264_mod.
If code 103 is taken out from the ValidHTTPCodes the 103 traffic is reported as not viewed traffic, ending up in a massive amount of not viewed bandwidth in the reports that looks very bad and not nice at all.
I've googled around but I couldn't find any reference to this problem anywhere.
Is anybody aware of this issue? I really need to solve it, any help is really appreciated.
Many thanks