I deployed this example[1] on a lambda with an application load balancer as a trigger. The request is not routed to the appropriate route if it is expecting some query params. The ALB actually strips all the query parameters and they can be found in the queryStringParameters attribute of the request event [2]. I tried updating the request handler [3], recreating the warp request to include the query parameters in the parts, but didn't have much luck with it.
[1] https://github.com/seanmonstar/warp/blob/d28154827b3f40e1d372758dc093829c09d3dce5/examples/query_string.rs
[2] https://docs.aws.amazon.com/elasticloadbalancing/latest/application/lambda-functions.html
[3] https://github.com/aslamplr/warp_lambda/blob/main/src/lib.rs#L101
I deployed this example[1] on a lambda with an application load balancer as a trigger. The request is not routed to the appropriate route if it is expecting some query params. The ALB actually strips all the query parameters and they can be found in the
queryStringParametersattribute of the request event [2]. I tried updating the request handler [3], recreating the warp request to include the query parameters in the parts, but didn't have much luck with it.[1] https://github.com/seanmonstar/warp/blob/d28154827b3f40e1d372758dc093829c09d3dce5/examples/query_string.rs
[2] https://docs.aws.amazon.com/elasticloadbalancing/latest/application/lambda-functions.html
[3] https://github.com/aslamplr/warp_lambda/blob/main/src/lib.rs#L101