This repository was archived by the owner on May 21, 2025. It is now read-only.
This repository was archived by the owner on May 21, 2025. It is now read-only.
Custom host (cont.) #31
Closed
Description
I saw that we made some effort to make the hostname more customizable (relevant issues: #21 and #13). I think we can make it even more flexible by allowing consumer to opt-in the option to use, wait for it, Host
header as the hostname.
In normal context, this is a terrible idea as Host
header can't be trusted at all. In APIG/Lambda context -- which is what this library is about -- I think it's an acceptable option. The reason being, API Gateway and CloudFront already reject all the requests with irrelevant Host
header. And those that hit Lambda are those that we can trust.
Hence, would using incoming Host
header as hostname be something we can consider as an option?
Metadata
Metadata
Assignees
Labels
No labels