sanfrancesco / prerendercloud-lambda-edge

Pre-render CloudFront with this Lambda@Edge function. Powered by https://headless-render-api.com (formerly named prerender.cloud from 2016 - 2022)
https://headless-render-api.com
MIT License
206 stars 35 forks source link

Lambda function invalid uri format. #13

Open matesio opened 6 years ago

matesio commented 6 years ago

I have deployed your lambda function with cloudfront distribution but when i try to pass query string it gives me error 502 lambda function invalid URI format.

Url: cloudforntdist.cloudfront.net/search?q=&subtype=subtype%20type&purpose=purpose&type=type

jotto commented 6 years ago

I am unable to reproduce this, can you send exact URL to support@prerender.cloud

also, was there a more interesting error message in the Cloudwatch logs?

matesio commented 6 years ago

Done, please check your mail.

hephalump commented 5 years ago

We are facing this same issue, with a fair degree of regularity. Sometimes it works, sometimes it doesn't. No changes to code or request... Our users randomly get this error.

image

jotto commented 5 years ago

Can you send an email to support@prerender.cloud with a few URLs I can investigate? I'll get it resolved within 48 hours.

matesio commented 5 years ago

hello @hephalump, in our case there were few failed calls which was very hectic to figure out. Same can be your case, check your logs for failed calls.

hephalump commented 5 years ago

@matesio I've checked the logs but don't see any failed calls. I'm wondering if this is a Lambda cold-start or Lambda@Edge with VPC issue - we've had Lambda containers take >15 seconds to load and execute on first invoke after going cold, and the behaviour we're experiencing is consistent with cold start behaviour... We know how to solve it in our region, not sure how to solve it @Edge.

jotto commented 5 years ago

@hephalump did you see my email responses to your email?

matesio commented 5 years ago

@hephalump same was in our case and finally had to remove lambda@edge from our production system because it was taking much time load even failing few calls.

hephalump commented 5 years ago

@jotto yes, responded to you.

@matesio we found an error in our logs