tunneller | Allow internal services , running on localhost , to be | Proxy library

I am trying to implement reverse SOCKS5 according to RFC1928. I have a relay server which runs passively waiting for connections from the SOCKS5 client which acts a proxy, and the the client which wants to use the tunnel.

Legend

Server (10.211.55.6) = Relay = PC 1 (send/recv)

Client_1 (10.211.55.10) = Proxy (running on another PC in my network)

Client_2 (10.211.55.8) = Tunneller (connecting from MaxThon Browser (since it allows SOCKS5 authentication))

Execution flow

1. Client_1 connects to Server on port 9444
2. Server finds an unused port and binds to it (lets say port 13451 is opened)
3. Client_2 connect to Server on port 13451
4. Server accepts the connection and now relays the traffic between Client_1 and Client_2
5. Client_2 sends the SOCKS5 protocol (according to RFC1928) requests to Client_1 relayed through Server
6. Client_1 authenticates and gets a CONNECT command to https://dnsleaktest.com and sends back a status_ok response
7. The packets from the webpage are received, and the webpage is loaded

Problem

1. Client_2 wants to connect to another webpage (lets take https://packetstormsecurity.com for example).

Question

Client_1 only receives a few packets from Client_2 such as \x17\x3\x3 or \x17\x3\x3\x1 (what do these bytes represent?). Does Client_1 have to go through the SOCKS5 authentication again, or how would it process the request to the new webpage?

Side Notes

A) After a while, the page that Client_2 requested from Client_1 returns ERR_TIMED_OUT in the browser, since Client_2 didn't get any response. But if its expecting a response, then its also assuming that I know how to parse the bytes that it sends, but I don't know what they are as I haven't seen them in the RFC1928 documentation.