How does tux redirect the request to the secondary server?

[shiner chen]

Tux should get client's http request before it can decide whether secondary server should handle the req. So client must have a complete socket connection with tux.
 
It is true that tux can insert a new socket into the accept queue of secondary server's listen socket. But the client just know the connection with tux. Secondary server is transparent for client. As a result, how client can receive the data from the secondary server? 
 
Yeah, we can use network hand-off or tcp splicing tech. to do that. But we must modify the tpc/ip protocol stack code. So is tux?
 
 Thanks much!!
 


Noah <sitz at onastick.net> wrote:
On Thu, Dec 02, 2004 at 09:33:38AM +0800, shiner chen wrote:
> Sorry, I dont get your answer's true point. I want to get your more detail explain.
> 
> 1.Does the secondary server send the response to client directly? Or secondary server send the response to tux because tux is a proxy for dynamic request?

The secondary server sends the response to the client directly.

> 2.if secondary server send response to client directly ,how does the tux implement that? I think tux must modify the tcp/ip protocol stack code. is it right?

Tux accepts the initial port 80 request, and makes a decision. If it
decides to let the secondary server handle the request, it picks up the
file descriptor which describes the network connection to the client and
hands it off to the secondary server. The server sends the response to
the client IP:port info in that file descriptor.

--n

-- 
dd of=/dev/fd0 if=/dev/flippy bs=1024
^^^ Making Flippy Floppy

_______________________________________________
tux-list mailing list
tux-list at redhat.com
https://www.redhat.com/mailman/listinfo/tux-list



---------------------------------
Do You Yahoo!?
注册世界一流品质的雅虎免费电邮
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/tux-list/attachments/20041202/37c37e79/attachment.htm>