Skip to content

Conversation

jackturnbull
Copy link
Contributor

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).
@jackturnbull jackturnbull force-pushed the feature/get-object-headers branch from b4f6f0c to fca8432 Compare April 4, 2019 21:59
@jackturnbull
Copy link
Contributor Author

@taylorfinnell apologies for the nudge, but any chance you can take a quick look at this one?

@taylorfinnell taylorfinnell merged commit 40d4022 into taylorfinnell:master Jun 24, 2019
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

Successfully merging this pull request may close these issues.

2 participants