Hans Maurer red.roses.de> writes:
> Actually, I was hoping for something like that when I wrote to the list. :-}
> I'll probably open a bug ticket for this.
>
>Hans
>
Hans
Looking at the responses to your bug/enhancement request to the apache list it
is clear the developers feel the necessa
Paul,
Paul Freeman schrieb:
There are already workarounds in apache and squid for certain non-compliant
behaviour of various browsers. Perhaps this is another case (although it is a
bit more fundamental given we are dealing with a protocol). There may even be a
solution using current settings
Hans Maurer red.roses.de> writes:
>
> Hi,
>
>
> Actually, my theory is more along the line that the basic design of RPC over
> HTTP is broken. It's extremely sensitive to any kind of delay or buffering
> on intermediary servers, and apache does exactly that (RFC compliant,
> nevertheless).
Hi,
Pieter Vanmeerbeek schrieb:
I tried to create a setup similar to the one Paul did (with https on the
internet and http on the secure lan). I couldn't get this working even
on the 2.0.53, ie. owa and active sync works fine RPC does some strange
things. If you wait a very long time ( more t
Pieter Vanmeerbeek able.be> writes:
>
> Hi Paul and Hans,
>
> I tried to create a setup similar to the one Paul did (with https on the
> internet and http on the secure lan). I couldn't get this working even
> on the 2.0.53, ie. owa and active sync works fine RPC does some strange
> things.
Hi Paul and Hans,
I tried to create a setup similar to the one Paul did (with https on the
internet and http on the secure lan). I couldn't get this working even
on the 2.0.53, ie. owa and active sync works fine RPC does some strange
things. If you wait a very long time ( more then5 minutes)
Hans Maurer red.roses.de> writes:
>
> Hi,
>
> I'm trying to grant road warrior users access to our company Exchange server
> through RPC over HTTP. In my setup, an Apache 2.2.2 on a FreeBSD server in
> the DMZ should act as a proxy between the Internet and the IIS on on the
> Exchange serve
