Re: [I] bug: aws-lambda plugin with IAM auth fails with URL-encoded query parameters [apisix]

[via GitHub]

kayx23 commented on issue #11097:
URL: https://github.com/apache/apisix/issues/11097#issuecomment-2064329613

   Meanwhile strangely I seem to be getting `400 Bad Request` for everything... 
this is the URL encoded example OP mentioned:
   
   
![image](https://github.com/apache/apisix/assets/39619599/41402a4f-3892-457a-afd3-fb24cecb90f6)
   
   Every request returned 400 and I'm quite baffled why. I also randomly 
changed secret key to a wrong value and lambda function endpoint. I expected to 
see different errors but all led to `400 Bad Request` with no further details 
on APISIX's log. This is my config:
   
   ![Screenshot at Apr 18 
23-31-32](https://github.com/apache/apisix/assets/39619599/db65b177-dc0d-48b7-b3c3-8d639f9b2b93)
   
   So I suspected the error came from upstream and specifically, due to CORS; 
because the lambda function worked fine when I tested on the AWS Console. The 
CORS setting was updated to allow all origins for the function URL:
   
   ![Screenshot at Apr 18 
23-43-06](https://github.com/apache/apisix/assets/39619599/231b2aac-d8bc-4b2f-9758-b0f88ab35ef7)
   
   Unfortunately this didn't help either.
   
   @deiwin Wondering if you have ever seen this issue before?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org