Hi there;
and thanks for your feedback. :)
Am Mittwoch, den 14.12.2016, 07:43 -0500 schrieb Jim Jagielski:
> I think that balancer-manager is exactly what you are looking for.
>
> http://httpd.apache.org/docs/2.4/howto/reverse_proxy.html#manager
>
Yes, I already stumbled across this - but th
Folks;
unsure whether this is the right place to ask and whether this is possible to
be accomplished out of
the box at all: So far we run an apache 2.4 mod_proxy balancer in front of
several backend services.
So far there are four backend instances configured into one balancer. This
works prett
Folks;
we use an apache2.4 and mod_proxy_balancer in front of various backend
systems that aren't per se able to deal with load balancers in front of
them so we use the approach outlined in [1] and mod_headers to set a
ROUTEID cookie.
What so far I was unable to figure out: How does this setup wo
Am 26.11.2014 um 15:19 schrieb Stefan Magnus Landrø:
Check user-agent header too. Mobile phones might just be too slow or get
disconnected
Did that already, but wasn't able to find a pattern here. Most of the
clients using our system use some desktop browser to upload larger files
or collect
Am 26.11.2014 um 14:48 schrieb Stefan Magnus Landrø:
I'd add response time logging %D to the access log config to see if requests
are slow
You can add that to jetty too.
I'll give it a try and see where it gets me - thanks for the hint!
Kristian
--
Hi Nick;
thanks for your comment.
Am 26.11.2014 um 14:11 schrieb Folino, Nick E CTR USARMY HRC (US):
You may need to enable chunked encoding for those locations.
SetEnv proxy-sendchunked
As far as I see in our configuration, chunked encoding is already
globally enabled. I remember o
Folks;
trying to track down a strange error, I am ending up here. Situation: We
run a web application built on top of Java and Jetty exposed through an
apache2 + mod_proxy reverse proxy.
Generally, this works fine. However, some of our users experience
troubles doing file uploads this way. I
Folks;
being into trying to extract meaningful information off an apache 2.2
access.log / error.log, I wonder whether there is a straightforward way here
of setting up logging so that only requests resulting in an HTTP STATE ==
40x or 5xx will be logged. Looking at access.log I see that the inform
Hi Rainer, *;
and first off, thanks for being patient enough reading through all the long
message to the very end, as well as for your comment on that. :)
Rainer Sabelka schrieb:
[...]
> I've observerd similar problems with large POST requests which sometimes time
> out on the backend servers wh
Folks;
dealing with this issue again; yet not really being capable of resolving it.
Maybe someone does have some more ideas on that. Scenario:
- apache 2.2 (Ubuntu 8.04) as reverse proxy in front of a glassfish v2
application server (seems to be unrelated to the latter one, though, same
issue app
Folks;
being into migrating one of our machines from Ubuntu 6.06/apache 2.0 to
Ubuntu 8.04/apache 2.2, I have hit some kind of issue in my
configuration regarding our reverse proxy environment. In our 2.0 setup,
we used to expose resources hosted on a backend system like this
ServerName foo.do
Hi all;
dealing with a peculiar problem in our environment, running apache 2.0.x
(Ubuntu 6.06.1) fronting our backend systems (tomcat 6.x, glassfish
v2u2) using mod_rewrite: In quite a bunch of situations we suffer from
ClientAbortExceptions like these whenever someone tries downloading a
larger b
12 matches
Mail list logo