SAP Knowledge Base Article - Preview

3804442 - [Integration Suite] Intermittent 'HTTP Stream 0' errors and no inbound hits caused by HTTP/2 connection-specific headers

Symptom

  • When a sender system posts to a Cloud Integration HTTP endpoint, it encounters intermittent "HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR”. 
  • No corresponding requests or hits are observed in BTP/Cloud Integration monitoring or system logs during the affected periods.


Read more...

Environment

  • SAP Integration Suite
  • SAP Cloud Integration

Keywords

HTTP Stream 0, HTTP/2 stream 0, PROTOCOL_ERROR, connection-specific header, keep-alive header, BTP, Cloud Integration, CPI, inbound HTTP, no hits in logs, proxy rewrite, HTTP/2, curl, HTTP/1.1 workaround, intermittent error, HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR, cpi, cloud integration, integration suite , KBA , LOD-HCI-PI-CON-HTP , HTTP Adapter , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.