Closed Bug 201045 Opened 21 years ago Closed 2 years ago

SSLInputStream.available() always returns 0

Categories

(JSS Graveyard :: Library, defect)

Product:
JSS Graveyard
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: jamie-bugzilla, Unassigned)

References

(Depends on 1 open bug)

Details

SSLInputStream.available() seems to always return 0. Perhaps it should be
implemented with PR_Available() instead of SSL_DataPending() ?
Status: NEW → ASSIGNED
Assignee: jamie-bugzilla → saul.edwards.bugs
Status: ASSIGNED → NEW
Target Milestone: --- → 4.0
I tested the available() in SSLInputStream implemented with SSL_DataPending(),
and cannot get it to report anything other than 0 bytes too.

However, PR_Available calls a plugin method from sslsock.c, ssl_available. 
Unfortunately, this method is not yet implemented.  Where should I go from here?
Nelson, do you have any suggestions on how to fix this
bug?
Please see bug 51409.

Yes, I do think JSS should call PR_Available instead of SSL_DataPending, 
but as bug 51409 explains, for an SSL socket, PR_Available usually returns
zero also.

I will add comments to bug 51409
Depends on: 51409
Status: NEW → ASSIGNED
Target Milestone: 4.0 → ---
QA Contact: jamie-bugzilla → jss-qa
Assignee: saul.edwards.bugs → nobody
JSS development has moved from the Mozilla community to the Dogtag PKI community. Please re-file this bug at https://github.com/dogtagpki/jss if it is still relevant. Thank you!
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.