Issue 8180 - back-sock should not return sucess in case of error
Summary: back-sock should not return sucess in case of error
Status: RESOLVED FIXED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: backends (show other issues)
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: 2.7.0
Assignee: Howard Chu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-29 12:27 UTC by Michael Ströder
Modified: 2024-01-12 21:55 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Michael Ströder 2015-06-29 12:27:10 UTC 
Full_Name: 
Version: HEAD
OS: 
URL: 
Submission from: (NULL) (84.181.173.53)


back-sock should definitely never return success(0) to the client in case the
external listener returned non-parseable message:

Example trace log:

55913915 => str2entry: "FOOBAR
msgid: 1
code: 49

"
55913915 <= str2entry NULL (parse_line)
55913915 str2entry: entry -1 has no dn
55913915 str2entry(FOOBAR) failed
55913915 sock: fgets failed: Success (0)
Comment 1 Quanah Gibson-Mount 2017-04-14 19:48:38 UTC 
moved from Incoming to Software Bugs
Comment 3 Quanah Gibson-Mount 2024-01-12 21:55:27 UTC 
  • 64789dd2 
by Howard Chu at 2023-11-14T17:02:18+00:00 
ITS#8180 back-sock: return error when str2entry fails


  • 66edd345 
by Howard Chu at 2023-11-14T17:02:18+00:00 
ITS#8677 back-sock: return error for CONTINUE