So i got my local server setup and everything cool until im using HTTP/2
I mean yall handle it pretty well but i don't know why the moment i put the header
"content-type: application/grpc" while using HTTP/2
oh yall get mad at me for some reason and give me error 464 with an empy response body
once i remove application/grpc everything works fine more than fine once i put it back yall dont like that why is that!!
Plus this never happen with HTTP/1 at all i can mess with grpc as much as i want.. but why not on HTTP/2
HTTP response status code 464 Incompatible protocol is an unofficial client error specific to AWS Elastic Load Balancer and used to indicate that the load balancer received an incompatible HTTP request protocol.
If it works with HTTP/1 then I would just stick with that. There are limitations within AWS that will prevent the use of some GRPC functionality when using HTTP/2 protocol. You could also look at using a private share, which might give you more control for what you need.
ive been using it on private share for test then got to use it on public one cause i need trusted SSL cert connection cause that's the my whole purpose of this, guess my only way now is by using a custom domain and going through a lot of setup stuff, i wished this could've worked well