Skip to content
This repository has been archived by the owner on Apr 13, 2023. It is now read-only.

Add X-SHA1 header #264

Open
tombentley opened this issue Mar 10, 2016 · 3 comments
Open

Add X-SHA1 header #264

tombentley opened this issue Mar 10, 2016 · 3 comments
Labels
enhancement
Milestone
1.25

Comments

@tombentley
Copy link

When serving artifacts if the Herd added at X-SHA1 HTTP response header it would save the CMR from having to make further request for the .sha1 file.
@FroMage FroMage added this to the 1.23 milestone Mar 10, 2016
@FroMage
Copy link
Contributor

FroMage commented Mar 10, 2016

VERY good point!

@quintesse
Copy link
Contributor

Nice idea!

@tombentley
Copy link
Author

A similar optimization would be a X-ExternalDescriptor: module.properties (or X-ExternalDescriptor: module.xml or X-ExternalDescriptor: none) header when the requested resource (currently always a .jar) had a related external module descriptor. Right now it looks like CMR has to make separate requests to find out if such an descriptor exists.

@FroMage FroMage modified the milestones: 1.23, 1.24 Sep 12, 2016
@FroMage FroMage modified the milestones: 1.24, 1.25 Apr 28, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
1.25
Development

No branches or pull requests
3 participants
@FroMage @quintesse @tombentley