You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 22, 2020. It is now read-only.
Break ZMON Controller API so it returns errors (e.g. because of broken auth configuration, so requests from data-service are not authorised)
Observe Index Out of Bounds Exception coming from de.zalando.zmon.dataservice.proxies.ControllerProxy#proxyForLastModifiedHeader
Explanation
When ZMON Controller API returns error responses, data-service still tries to get "Last-Modified" header from there and fails. Need to make sure that data-service tries to check if the header in the response before it tries to extract it.
Acceptance criteria
Instead of Out of Bounds Exception data-service must report that "Last-Modified" header was not found and provide response data, so it's easier for developers to investigate
The text was updated successfully, but these errors were encountered:
elgris
added
the
bug
user-reported issues that take more than one hour to resolve
label
Aug 22, 2017
How to reproduce
de.zalando.zmon.dataservice.proxies.ControllerProxy#proxyForLastModifiedHeader
Explanation
When ZMON Controller API returns error responses, data-service still tries to get
"Last-Modified"
header from there and fails. Need to make sure that data-service tries to check if the header in the response before it tries to extract it.Acceptance criteria
"Last-Modified"
header was not found and provide response data, so it's easier for developers to investigateThe text was updated successfully, but these errors were encountered: