I'm not familiar with mod_jk. In general web servers will handle url lengths between 2k and 4k, in line with browser limits.
On Sat, May 2, 2009 at 3:02 AM, Ian Boston <[email protected]> wrote: > Kevin, > A related question, you might have some insights into: > Are there any issues with the URL size and the gadget end points that would > prevent a mod_jk front end working? > I have heard rumors that mod_jk chokes on very large URL's but I have not > been able to validate. > Ian > > > > On 2 May 2009, at 09:47, Kevin Brown wrote: > > The way you would normally implement something like this is by using a >> reverse proxy in front of both of your back ends. Apache httpd, >> lighthttpd, >> and squid are all pretty good at this for most usage. There are more >> specialized projects as well. >> >> squid will generally perform the best of these options, though httpd (with >> mod_proxy) is generally easiest to set up. >> >> On Fri, May 1, 2009 at 7:54 PM, jay patel <[email protected]> wrote: >> >> Hi Shindig Team, >>> >>> I am trying to run gadgets and social projects on separate servers. As >>> javascripts for social feature is served by the "gadgets server" (and, >>> not >>> by the "social server"), browser complains when javascript for social >>> feature tries to access rest/rpc services from "social server". Is there >>> any >>> solution implemented in current shindig (such as proxy/jsonp...etc) to >>> overcome this. >>> >>> I really do not want gadget and social projects on one server >>> instance...I >>> want to keep "gadget server" and "social rest/rpc server" separate. >>> >>> My gadget server is running on localhost:8080 and social server on >>> localhost:8081..both servers are Jetty. I am using the latest code from >>> the >>> trunk. >>> >>> Thanks for your time, >>> >>> Jay >>> >>> >
