no offense to the OP, but i love Maxim. Direct and to the point, and in
this case, as usual, he is correct. You should not look at what the
requester wants, before understanding what the sender should provide.

On Thu, Jun 25, 2020 at 2:18 PM Maxim Dounin <mdounin@mdounin.ru> wrote:

> Hello!
>
> On Thu, Jun 25, 2020 at 02:02:35PM -0400, anish10dec wrote:
>
> > Thanks Maxim
> >
> > Actually null character is not being generated by Client .
> >
> > We are using below module to validate the tokens
> > https://github.com/kaltura/nginx-akamai-token-validate-module
> >
> > This is being caused by akamai_token_validate_strip_token directive which
> > strips the token and forwards request to upstream server.
> >
> > While striping the token and passing the remaining request to upstream
> > stream its appending null character at the end.
> > If there is no any additional query param in request apart from token ,
> then
> > there is no issue in handling.
> >
> >
> http://10.49.120.61/folder/Test.m3u8?token=st=1593095161~exp=1593112361~acl=/*~hmac=60d9c29a65d837b203225318d1c69e205037580a08bf4417d4a1e237e5a2f5b6&uid=abc123
> >
> > Request passed to upstream is as below which is causing problem
> >
> > GET /folder/Test.m3u8?uid=abc123\x00
>
> So the module is broken and needs to be fixed.
>
> --
> Maxim Dounin
> http://mdounin.ru/
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx