Opened 11 years ago

#1081 closed defect (Implemented)

Winsock errors are logged incorrectly

Reported by: loafier Owned by: loafier
Priority: Low Milestone:
Component: Polipo Version: 1.0
Severity: Keywords:
Cc: loafier Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Polipo doesn't log Winsock errors correctly, because it seems to indirectly
pass the result of WSAGetLastError() to strerror().

Some typical messages:
Couldn't read from client: Unknown error
Couldn't read from client: Unknown error

"Unknown error" in the above case should be
"Software caused connection abort." (err = WSAECONNABORTED, code = 10053)
or "Connection reset by peer." (err = WSAECONNRESET, code = 10054)

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (1)

comment:1 Changed 11 years ago by loafier

flyspray2trac: bug closed.

Note: See TracTickets for help on using tickets.