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

Improved generation of HEAD request #12

Closed
koenedaele opened this issue Nov 3, 2015 · 7 comments
Closed

Improved generation of HEAD request #12

koenedaele opened this issue Nov 3, 2015 · 7 comments

Comments

@koenedaele
Copy link
Member

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.

@koenedaele koenedaele added this to the Further down the road milestone Nov 3, 2015
@koenedaele koenedaele changed the title Imporved generation of HEAD request Improved generation of HEAD request Nov 3, 2015
@BartSaelen
Copy link
Contributor

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.

@BartSaelen
Copy link
Contributor

@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.

@kmillet
Copy link
Contributor

kmillet commented Feb 3, 2016

see #15

@koenedaele
Copy link
Member Author

@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.

@BartSaelen
Copy link
Contributor

Making Augeias mime-type aware would be nice, but this problem has other roots I think (see #15)

@claeyswo
Copy link
Member

Solved by #23 no?

@claeyswo
Copy link
Member

Solved by #23 no?

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

No branches or pull requests

4 participants