Skip to content

vlts recv, use full buffer size if possible #10736

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.

Sign up for GitHub

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

Jump to bottom
Closed
icing wants to merge 1 commit into from
Closed

vlts recv, use full buffer size if possible #10736

icing wants to merge 1 commit into from

Conversation

@icing
Copy link
Contributor

@icing icing commented Mar 10, 2023

SSL backends like OpenSSL/wolfSSL and other return the content of one TLS record on read, but usually there are more available.

Change the vtls cfilter recv() function to fill the given buffer until a read would block.

@icing
vlts recv, use full buffer size if possible
f621bd8 
SSL backends like OpenSSL/wolfSSL and other return the content of
one TLS record on read, but usually there are more available.

Change the vtls cfilter recv() function to fill the given buffer
until a read would block.
@bagder
Copy link
Member

bagder commented Mar 30, 2023

Thanks!

@bagder bagder closed this in b74bba9 Mar 30, 2023
bch pushed a commit to bch/curl that referenced this pull request Jul 19, 2023
@icing @bch
vlts: use full buffer size when receiving data if possible
af9e6e9 
SSL backends like OpenSSL/wolfSSL and other return the content of one
TLS record on read, but usually there are more available.

Change the vtls cfilter recv() function to fill the given buffer until a
read would block.

Closes curl#10736
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@bagder bagder bagder approved these changes

Assignees

No one assigned

Labels

TLS

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@icing @bagder