You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using nginx-vod-module version 1.33 to access remote content in HLS.
As I'm using tokens (verified by a Lambda function in an Amazon CloudFront distribution) urls can be quite long.
I configured vod module so as it removes the token part from url before calling the remote server, but token must be preserved in manifest and segment urls.
When the length of urls achieves a certain value, an error 500 is returned: m3u8_builder_build_master_playlist: result length 2265 exceeded allocated length 2263 while sending to client
Removing some characters makes it work fine again.
This is a minimal configuration to reproduce the problem. In this case local server is acting as the remote one:
I'm using nginx-vod-module version 1.33 to access remote content in HLS.
As I'm using tokens (verified by a Lambda function in an Amazon CloudFront distribution) urls can be quite long.
I configured vod module so as it removes the token part from url before calling the remote server, but token must be preserved in manifest and segment urls.
When the length of urls achieves a certain value, an error 500 is returned:
m3u8_builder_build_master_playlist: result length 2265 exceeded allocated length 2263 while sending to client
Removing some characters makes it work fine again.
This is a minimal configuration to reproduce the problem. In this case local server is acting as the remote one:
I debugged the code and I've seen that in https://github.com/kaltura/nginx-vod-module/blob/1.33/vod/hls/m3u8_builder.c#L1420 the contribution to result_size due to iframe playlist does not increase when the length of the url increases. I guess that for short urls, the value of result_size is oversized enough from contributions in https://github.com/kaltura/nginx-vod-module/blob/1.33/vod/hls/m3u8_builder.c#L1415 and causes no problem.
The text was updated successfully, but these errors were encountered: