For a deeper look into our Elektron API, look into:
Overview | Quickstart | Documentation | Downloads | Tutorials | Articles
Hi team,
Regards the NFD feed, last 3 days ( never happened before ) we observed that NFD server sent us the response with NULL header around 05:00 am EST time.
Could you help to take a look ?
We follow the TRNA client example from Thomson Reuter and it handles the NULL header by exiting the app. Please confirm if the null header event happens regularly we need to make the code changed for it
Hi @wqdata
The 'header' you are referring to is HTTP header when using HTTP client interface of NFD feed, and not the new message header when using the new MRN feed, is this correct?
Hi @wqdata
Since this seems to be data issue. I have created a support ticket and escalated it to NFD feed support on your behalf.
The ticket id is 05422877. The support will contact you back.
According to the case: 05422877 opened to NFD support, the issue cannot be reproduced. If there is any more issue, the client will contact the support team directly.
Resolution Comment:
Checked our systems, ran client with same ents and could not reproduce the problem. Recommended client run network capture and check their app. No fault found on our side. Client modified his app and gave positive closure
Moved from the "Alpha" forum to "Elektron". This is not perfect but a bit more appropriate.
Issue status:
This issue seems to be data related and has been raised to the NFD feed support (June-29). The support team has not been able to reproduce. The client will recontact the support team with network captures if the issue happens again.
