support for http/2 based APIs

[ajithr1990]

Hello Team,

We have been trying to set up apigee prioxy to communicate with Apple push notification http/2 API. But every time we try establish a connection , it fails at SSL handshake and gives us a response

- {"fault":{"faultstring":"Unexpected EOF at target","detail":{"errorcode":"messaging.adaptors.http.flow.UnexpectedEOFAtTarget"}}}.

Connecting to http1.1 based apis are working fine and never faced any issues with it.

Is http/2 the problem here. And what is the solution to fix this.

[yishail]

Not sure how much this response is an answer, or a direction down a rabbit hole:
Explanation about HTTP/2 SSL transaction, and introduction to a concept named ALPN:
https://matthewparrilla.com/post/negotiation-http2-alpn-tls-handshake/

Basically, you need to ensure that NGINX can provide ALPN connectivity. If you're fully on cloud - you are fully dependent on Google/Apigee. If you're on private cloud - it might be worth while to check how to get your local NGINX to provide this ALPN connectivity (I saw something about OpenSSL version, but I've only read the posts, haven't tried), and then see what Google say about tailoring your servers re. general Apigee support.

Good Luck!

[dchiesa1]

I think the connection here is Southbound, at the target endpoint. If that is correct, then nginx would not be involved.