Hi,
There are at least 3 different approaches for configuring Apache httpd 2.2
to act as a reverse proxy for Tomcat 7.0:
a) mod_proxy_http
b) mod_proxy_ajp
c) mod_jk
There's been quite a lot of discussion about the differences of each one
but a lot of that discussion appears to be either not ver
On 31/10/2012 20:08:21 GMT, Mark Thomas wrote:
> http://www.tomcatexpert.com/blog/2010/06/16/deciding-between-modjk-modproxyhttp-and-modproxyajp
>
> The mod_proxy_ajp stability issues are less of an issue now than they
> were when I wrote that article. What that means is if you want the SSL
> bene
Chris Schultz wrote:
> On 10/31/12 3:55 PM, Marko Asplund wrote:
> > There are at least 3 different approaches for configuring Apache
> > httpd 2.2 to act as a reverse proxy for Tomcat 7.0:
> >
> > a) mod_proxy_http b) mod_proxy_ajp c) mod_jk
> >
> > ...
&
Hi,
I'm just starting out with using the Servlet 3.1 asynchronous processing
API.
I use the API for generating response content, that can potentially be a
slow process, in another thread.
The code appears to be working, but since the specification contains many
caveats, I'd like to try and verify
On Wed, 09 Jul 2014 07:23 Martin Grigorov wrote:
> > ...
> > try {
> > response = (HttpServletResponse)asyncContext;
> >
>
> Maybe it is implementation detail that this cast works but usually you
have
> to use
>
http://docs.oracle.com/javaee/6/api/javax/servlet/AsyncContext.html#
Hi,
We're developing webapps running on Tomcat 7. The apps use third-party
components that we can't modify and those components connect to external
sites using HTTP.
Our ops guys have a policy of routing all outbound traffic through an
authenticating HTTP proxy.
This is a bit of problem for us sin
On 09/07/2014 09:16, Mark Thomas wrote:
> > There's a couple of parts in particular that I'm wondering about:
> > - what's the correct way to deliver error response to client? Can I just
> > cast the response acquired from AsyncContext to HttpServletResponse and
use
> > the normal Servlet API mech
On Wed, 09 Jul 2014 09:59 Martin Grigorov wrote:
> Casting ServletResponse to HttpServletResponse is OK most of the time. You
> can check with "instanceof" before doing the cast.
> But casting AsyncContext to HttpServletResponse is way too brave.
Quite true, I'm not usually that courageous on pur
sin 4.0.40.
What could be causing this? A bug in my servlet code?
The code and results can be found here:
https://github.com/marko-asplund/servlet3-async
marko
