-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add "HTTP 464 error with AWS" to the FAQ #67
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
cc @akshayjshah |
Co-authored-by: Michael Rebello <[email protected]>
docs/faq.md
Outdated
If you need both the Connect and gRPC protocols, you can use two target groups: | ||
Route HTTP GET requests and anything with the `application/proto`, `application/json`, | ||
`application/connect+proto`, or `application/connect+json` Content-Types to the | ||
HTTP/2 target group. Route anything else to the gRPC target group. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure how to keep the text short, but I found this explanation a little misleading. Even if the user needs support for gRPC, they can continue to use an HTTP/2 target group - as far as I know, their RPCs will work just fine. However, they'll give up support for the gRPC-specific add-on features that gRPC target groups provide.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call. I expanded it to clarify.
No description provided.