Skip to content
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

Merged
merged 5 commits into from
Nov 3, 2023
Merged

Conversation

timostamm
Copy link
Member

No description provided.

@vercel
Copy link

vercel bot commented Oct 9, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
connect ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 1, 2023 0:46am

docs/faq.md Show resolved Hide resolved
docs/faq.md Outdated Show resolved Hide resolved
docs/faq.md Outdated Show resolved Hide resolved
@rebello95
Copy link
Contributor

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.
Copy link
Member

@akshayjshah akshayjshah Oct 10, 2023

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.

Copy link
Member Author

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.

@akshayjshah akshayjshah merged commit 3551d3b into main Nov 3, 2023
@akshayjshah akshayjshah deleted the tstamm/add-aws-faq branch November 3, 2023 21:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants