-
Notifications
You must be signed in to change notification settings - Fork 1
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
Improved generation of HEAD request #12
Comments
Correct meta data is not passed to the client because the use of content_type='application/octet-stream'. The content-length header is not passed in this case. |
@kmillet can you describe the problem with the HEAD request and content-length header in a separate bug issue. Not sure this is entirely related. |
see #15 |
@BartSaelen Is the easiest solution making Augeias mime-type aware? So that we can send correct Content Type headers? That way downstream apps don't need to keep mime-types around like they have to do now. |
Making Augeias mime-type aware would be nice, but this problem has other roots I think (see #15) |
Solved by #23 no? |
Solved by #23 no? |
See #9 . Currently, the server fetches the entire object, generates metadata and then throws away the object. Saves some bandwith between the client and Augeias, but can probably be made more efficient between Augeias and the store.
The text was updated successfully, but these errors were encountered: