403Webshell
Server IP : 77.68.64.21  /  Your IP : 216.73.216.219
Web Server : Apache
System : Linux hp3-wp-1011378.hostingp3.local 3.10.0-1160.144.1.el7.tuxcare.els9.x86_64 #1 SMP Fri Jul 10 17:06:31 UTC 2026 x86_64
User : csh2668128 ( 2112425)
PHP Version : 8.1.34
Disable Function : shell_exec,exec,system,popen,set_time_limit
MySQL : OFF  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : ON  |  Sudo : ON  |  Pkexec : ON
Directory :  /usr/share/doc/haproxy-1.5.18/internals/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :


[ Back ]     

Current File : /usr/share/doc/haproxy-1.5.18/internals/connect-status.txt
Normally, we should use getsockopt(fd, SOL_SOCKET, SO_ERROR) on a pending
connect() to detect whether the connection correctly established or not.

Unfortunately, getsockopt() does not report the status of a pending connection,
which means that it returns 0 if the connection is still pending. This has to
be expected, because as the name implies it, it only returns errors.

With the speculative I/O, a new problem was introduced : if we pretend the
socket was indicated as ready and we go to the socket's write() function,
a pending connection will then inevitably be identified as established.

In fact, there are solutions to this issue :

  - send() returns -EAGAIN if it cannot write, so that as long as there are
    pending data in the buffer, we'll be informed about the status of the
    connection

  - connect() on an already pending connection will return -1 with errno set to
    one of the following values :
      - EALREADY : connection already in progress
      - EISCONN  : connection already established
      - anything else will indicate an error.

=> So instead of using getsockopt() on a pending connection with no data, we
   will switch to connect(). This implies that the connection address must be
   known within the socket's write() function.



Youez - 2016 - github.com/yon3zu
LinuXploit