Nope.
My test client is a Perl SOCKET level IO deal and I am able
to send EXACTLY what was in your email as the 'fake' Treo
request, including the 'messed up' Host:redowadev.esri.com
header which is missing the SPACE character after the colon.
Doesn't make any difference here.
Apache
I have a feeling you have other components in play here and one
of them might be the culprit that is always adding the 'Connection: close'
to the OPTIONS request. Some home-grown and/or commercial filter or
something? Another ( invisible/broken ) Proxy in the mix that's automatically
adding
Believe I may have this working now.
The Treo was sending its Host header as follows:
Host:hostname.esri.com
(Note the lack of space betwen the colon and hostname. This probably
isn't valid but was corrected by Apache as it proxied the request on to
IIS. However, maybe the initial invalid
I tried digging into the code a bit with gdb with mixed results. The
Treo actually would sync up properly sometimes even without the Host
fix in place as long as I was running in gdb. Maybe some sort of
timing issue?
Anwyays, I never saw it hit a backend-close = 1 line -- at least not
in
Late reply on this -- I had to spend time on other projects. :) I have
a dedicated test proxy set up now so it's easier to capture the correct
packets now and experiment.
Sounds you are just stuck in the middle trying to deal with a broken
client. I thought you might be trying to actually
On Thu, May 22, 2008 at 01:32:25AM -0700, Ruediger Pluem wrote:
On 05/22/2008 03:05 AM, Ray Van Dolson wrote:
I'm having a heck of a time getting Palm Treo's to work through our
Apache 2.2.3 based proxy talking to an OWA2K7 setup running on IIS. I
believe I may be getting pinched
On Thu, May 22, 2008 at 08:53:41AM -0700, Ray Van Dolson wrote:
On Thu, May 22, 2008 at 01:32:25AM -0700, Ruediger Pluem wrote:
On 05/22/2008 03:05 AM, Ray Van Dolson wrote:
I'm having a heck of a time getting Palm Treo's to work through our
Apache 2.2.3 based proxy talking
On Thu, May 22, 2008 at 01:52:11PM -0700, Jim Jagielski wrote:
On May 21, 2008, at 9:05 PM, Ray Van Dolson wrote:
As I said, everything works fine this way. With mod_proxy in the mix
however:
1 TREO Sends OPTIONS request to Apache (Connection: Keep-Alive)
2 Apache Sends OPTIONS
On Thu, May 22, 2008 at 02:59:41PM -0700, Jim Jagielski wrote:
On Thu, May 22, 2008 at 01:59:30PM -0700, Ray Van Dolson wrote:
I promise to go and read through the RFC's, but if the Treo is
requesting a Keep-Alive connection, shouldn't Apache try its best not
to close the connection
My most feasible option is to try and see if this is something that can
be addressed within Apache. An option to allow a persistent connection
in the scenario above might help.
Try to get the Treo into different connection-handling logic
altogether and see if that helps. Maybe
On Thu, May 22, 2008 at 09:03:23PM -0700, [EMAIL PROTECTED] wrote:
Your posts keep saying The Treo does this and the Treo does
that and likelihood of fixing Treos is 0 percent...
...but I'm a little confused.
What SOFTWARE are we talking about on the Treo.
The Treo is just a handheld.
I'm having a heck of a time getting Palm Treo's to work through our
Apache 2.2.3 based proxy talking to an OWA2K7 setup running on IIS. I
believe I may be getting pinched by:
https://issues.apache.org/bugzilla/show_bug.cgi?id=43238
The Treo seems to work fine without a proxy. I observe the
12 matches
Mail list logo
