What's the thoughts of the dev group on maintaining an accessor
similar to $c->req->base and $c->req->uri that reflects the internal
base/uri when running behind a proxy.
The /achieve is quite simple, behind a load balancer/proxy I have app
instances that communicate to a backend service and the backend
service needs to send requests back to each individual node (for
caching purposes, in this example).
When the nodes make the connection to the internal service, I'm
passing in the internal path so the internal path is then able to push
back status flags.
Thoughts on this?
-J
_______________________________________________
Catalyst-dev mailing list
Catalyst-dev@lists.scsys.co.uk
http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst-dev
similar to $c->req->base and $c->req->uri that reflects the internal
base/uri when running behind a proxy.
The /achieve is quite simple, behind a load balancer/proxy I have app
instances that communicate to a backend service and the backend
service needs to send requests back to each individual node (for
caching purposes, in this example).
When the nodes make the connection to the internal service, I'm
passing in the internal path so the internal path is then able to push
back status flags.
Thoughts on this?
-J
_______________________________________________
Catalyst-dev mailing list
Catalyst-dev@lists.scsys.co.uk
http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst-dev