[#1471] eacl: Don't process object headers twice in response processing
It is redundant to process object headers in responses w/o object field since result will be the same. Signed-off-by: Leonard Lyubich <leonard@nspcc.ru>
This commit is contained in:
parent
8b94cb22d3
commit
f9504c1cba
1 changed files with 0 additions and 3 deletions
|
@ -143,9 +143,6 @@ func (h *cfg) objectHeaders() ([]eaclSDK.Header, error) {
|
||||||
}
|
}
|
||||||
case responseXHeaderSource:
|
case responseXHeaderSource:
|
||||||
switch resp := m.resp.(type) {
|
switch resp := m.resp.(type) {
|
||||||
default:
|
|
||||||
hs, _ := h.localObjectHeaders(h.cnr, h.obj)
|
|
||||||
return hs, nil
|
|
||||||
case *objectV2.GetResponse:
|
case *objectV2.GetResponse:
|
||||||
if v, ok := resp.GetBody().GetObjectPart().(*objectV2.GetObjectPartInit); ok {
|
if v, ok := resp.GetBody().GetObjectPart().(*objectV2.GetObjectPartInit); ok {
|
||||||
oV2 := new(objectV2.Object)
|
oV2 := new(objectV2.Object)
|
||||||
|
|
Loading…
Reference in a new issue