httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 32737] New: - apr_socket_addr_get(APR_REMOTE) doesn't work after apr_socket_connect(), if the socket is non-blocking
Date Thu, 16 Dec 2004 16:48:08 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32737>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32737

           Summary: apr_socket_addr_get(APR_REMOTE) doesn't work after
                    apr_socket_connect(), if the socket is non-blocking
           Product: APR
           Version: HEAD
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: APR
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: inoue@ariel-networks.com


step:
1. create a socket with non-blocking mode
2. call apr_socket_connect()
3. make sure the connection established
4. call apr_socket_addr_get() to get APR_REMOTE socket-address,   but it doesn't
work.

solution:
sock->remote_addr_unknown should be TRUE at initialization.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message