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 basic support for protocol v2 #710

Closed
wants to merge 15 commits into from
Closed

Add basic support for protocol v2 #710

wants to merge 15 commits into from

Conversation

jaclarke
Copy link
Member

@jaclarke jaclarke commented Aug 2, 2023

No description provided.

@jaclarke jaclarke mentioned this pull request Aug 2, 2023
2 tasks
@scotttrinh scotttrinh changed the base branch from master to fix-multirange-anytype October 26, 2023 23:44
Base automatically changed from fix-multirange-anytype to master October 27, 2023 14:17
scotttrinh and others added 4 commits August 29, 2024 20:37
@diksipav diksipav self-assigned this Aug 30, 2024
I will try to add these tomorrow:

Documentation is missing:
- SNI,
- Cloud Profile,
- tlsCA maybe should be documented too,
- `credentials` is not documented.

**More things to be done**: add SNI to credentials.json in the cli, and
later read it from there: `Oh and to address this specifically, although
very marginal, we may want to update the CLI to include tls_server_name
in credentials.json if --tls-server-name was specified while linking an
instance.`

Atm CLOUD_PROFILE is taken from env var when using options. And when
using env vars it is not used at all?

---------

Co-authored-by: Scott Trinh <scott@edgedb.com>
jaclarke added a commit to edgedb/edgedb that referenced this pull request Sep 4, 2024
…ersion in the response `content-type` header (#7701)

Currently the `content-type` header of the response for the binary over
http protocol, always contains the latest protocol version supported by
the server, even if the client requested an older protocol version and
the response data actually being encoded using that requested version.

The current edgedb-js client which still uses protocol v1, just happens
to work despite this bug, as it also has a bug that results in it
ignoring the incorrect protocol version header from the server and
assuming it's the version requested. (Will be fixed in
edgedb/edgedb-js#710)
@scotttrinh
Copy link
Collaborator

Closed in favor of #1091

@scotttrinh scotttrinh closed this Oct 30, 2024
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