Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lambda function invalid uri format. #13

Open
matesio opened this issue Jun 27, 2018 · 9 comments
Open

Lambda function invalid uri format. #13

matesio opened this issue Jun 27, 2018 · 9 comments

Comments

@matesio
Copy link

matesio commented Jun 27, 2018

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
Copy link
Collaborator

jotto commented Jul 2, 2018

I am unable to reproduce this, can you send exact URL to [email protected]

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

@matesio
Copy link
Author

matesio commented Jul 2, 2018

Done, please check your mail.

@matesio matesio closed this as completed Jul 2, 2018
@matesio matesio reopened this Jul 2, 2018
@matesio matesio closed this as completed Jul 10, 2018
@hephalump
Copy link

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 jotto reopened this Feb 22, 2019
@jotto
Copy link
Collaborator

jotto commented Feb 22, 2019

Can you send an email to [email protected] with a few URLs I can investigate? I'll get it resolved within 48 hours.

@matesio
Copy link
Author

matesio commented Feb 26, 2019

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
Copy link

@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
Copy link
Collaborator

jotto commented Feb 26, 2019

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

@matesio
Copy link
Author

matesio commented Feb 26, 2019

@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
Copy link

@jotto yes, responded to you.

@matesio we found an error in our logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants