backward forward

[Trustin Lee (이희승)]

Hi Gabi,

If the file is located in the other server, I'd send a response code
301 or 302 (moved permanently or found) so that the client can retry
with the suggested new URL.

If you do not want the client to send another request, you will have
to forward the request to the other server, which is somewhat tricky.
You might find the proxy example useful.

HTH

— Trustin Lee, http://gleamynode.net/



On Fri, Oct 16, 2009 at 12:34 AM, gciuloaica <gciuloaica at gmail.com> wrote:
>
> Hi,
>
> I have the following situation:
> there are 2 instances of Http File Server example, that serves files from 2
> machines. Each instance is running on its own hardware. Both are connected
> to internet through a load balancer that is using round robin to distribute
> requests on those 2 machines. If the user is requesting file A, load
> balancer will fwd the request to machine 1 but the file A is not on machine
> 1 but on machine 2. One way to solve the issue is to fwd the request from
> one netty instance to the other but not sure how optimal is this approach
> and second, I do not know how to implement it.
>
> Any help or comments are greatly appreciated.
>
> Thanks,
> Gabi
> --
> View this message in context: http://n2.nabble.com/backward-forward-tp3830055p3830055.html
> Sent from the Netty User Group mailing list archive at Nabble.com.
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
>