Thanks Maxim
Will fix the module , just was looking a way around if it can be handled by
just removing the null character
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,288455,288472#msg-288472
___
nginx mailing list
nginx@nginx.org
http://m
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 wrote:
> Hello!
>
> On Thu, Jun 25, 202
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 akam
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 t
Hello!
On Thu, Jun 25, 2020 at 11:33:29AM -0400, anish10dec wrote:
> Nginx Upstream returning 400 Bad Request if null character is being passed
> in the request as part of uri or query params.
>
> Is there a way Null Character can be removed from request before proxying
> it to upstream.
>
> I
Nginx Upstream returning 400 Bad Request if null character is being passed
in the request as part of uri or query params.
Is there a way Null Character can be removed from request before proxying
it to upstream.
Its only known from access logs that null character is being passed in
request as \x
