Having the headers in this response object could be useful for cases where the object store has more knowledge about the object than the Crystal process (e.g. Crystal acting as a wildcard proxy to S3 to authorise requests).
I've got this current use case, as I'm effectively using S3 as my filesystem but when I wish to proxy a file back to a client I need to scan the file path for the extension so that I can set the Content-Type, which feels like a waste when it's already delivered from S3.
Any thoughts let me know, but hoping it's not a controversial one! 😄
Having the headers in this response object could be useful for cases where the object store has more knowledge about the object than the Crystal process (e.g. Crystal acting as a wildcard proxy to S3 to authorise requests).
I've got this current use case, as I'm effectively using S3 as my filesystem but when I wish to proxy a file back to a client I need to scan the file path for the extension so that I can set the Content-Type, which feels like a waste when it's already delivered from S3.
Any thoughts let me know, but hoping it's not a controversial one! 😄