Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
GnuTLS
GnuTLS
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 213
    • Issues 213
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 12
    • Merge Requests 12
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • gnutls
  • GnuTLSGnuTLS
  • Issues
  • #806

Closed
Open
Opened Jul 24, 2019 by Michael Catanzaro@TheRealMichaelCatanzaroContributor

Minor inaccuracy in gnutls_record_send() documentation?

The documentation of gnutls_record_send() says:

If  GNUTLS_E_INTERRUPTED  or
GNUTLS_E_AGAIN is returned, you must call this function again, with the
exact  same  parameters; alternatively you could provide a NULL pointer
for data, and 0 for size. cf. gnutls_record_get_direction().

But I think this is no longer accurate since gnutls_record_discard_queued() was added. Now you have three choices: call with exact same parameters, call with NULL and 0, or call gnutls_record_discard_queued() and then call gnutls_record_send() with whatever you want. Correct?

Proposed revised text:

If GNUTLS_E_INTERRUPTED or GNUTLS_E_AGAIN is returned, you must call this
function again with the exact same parameters, or provide a NULL pointer
for data and 0 for size, in order to write the same data as before. If you
wish to discard the previous data instead of retrying, you must call
gnutls_record_discard_queued() before calling gnutls_record_send() with
different parameters.
Assignee
Assign to
Release of GnuTLS 3.6.10
Milestone
Release of GnuTLS 3.6.10 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gnutls/gnutls#806