Hello Jim, Note that Proxy will also be communicating with Origin Server (OS) where the content is going to come from. At AS, I am just expecting to process the content received from OS. So in this context, I am looking at this AS as an extension of Proxy server.
On other words, theoretically I can implement a module and put all the logic in the AS, but I can't do that. So I offloading the task to AS. So I need this module in between which will talk to the AS (HTTP Servlet on the Tomcat). Once the message is processed by AS, I can then send it either to OS or to Client depending on the type of message. I am not sure how does mod_proxy and mod_proxy_http works in this scenario. I am new to the Apache HTTP architecture. So having all the basic doubts. /anil. On Wed, Mar 6, 2013 at 3:17 PM, Jim Jagielski <j...@jagunet.com> wrote: > > Hello Nick, > > > > Thanks for your reply. I am trying to understand what could be the > interface between Proxy Server (PS) and App Server (AS) given that App > Server is a Tomcat based HTTP Servlet. Proxy Server is going to be a > mod_xxx written in C. > > > > So my question is, what interface will be used between PS and AS? I read > about mod_proxy, mod_proxy_ajp, but they mainly provide the load balancer > or reverse proxy functionality. I want this PS to route the HTTP traffic > between Client and OS to this AS for processing. > > > > Anil, > > The protocol used between PS and AS can either be HTTP > or AJP, depending on what listener you have setup on Tomcat. > Obviously, if you are using the AJP listener on AS, you'd > need to ProxyPass ajp; if using HTTP, then it would be > ProxyPass http:. Proxying ajp requires mod_proxy_ajp and > proxying http requires mod_proxy_http > > > I hope this makes my question more clear. Sorry for it not being very > specific earlier. > > > > Thanks, > > > > /anil. > > > > On Wed, Mar 6, 2013 at 1:28 PM, Nick Kew <n...@webthing.com> wrote: > > > > On 6 Mar 2013, at 18:11, Anil J wrote: > > > > > Hi, can anyone comment on this? > > > > You haven't told us where the problem is. The things you describe > > are just standard applications. > > > > -- > > Nick Kew > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > > For additional commands, e-mail: users-h...@httpd.apache.org > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > >
