On Wed, 3 Jul 2013 15:26:16 +0200, Lieven Govaerts <lgo_at_apache.org> said:
> On Tue, Jun 25, 2013 at 11:17 PM, Lieven Govaerts
> <lieven.govaerts_at_gmail.com> wrote:
>> On Tue, Jun 25, 2013 at 9:37 PM, Greg Stein <gstein_at_gmail.com> wrote:
>>> This is normally a question for users@, but I think Lieven was working
>>> on something exactly like this already. I've cc'd him for more detail.
>> Ashish already reported this in the serf issue tracker:
>> The reason I asked him to report here, is that I think the issue
>> scenario can be summarized to this:
>> svn+ra_serf using an ssl tunnel don't work if the server has KeepAlive
>> off. The error reported is '501 Not Implemented'.
>> Such status code is not handled within serf or subversion.
>> Now I'm trying to reproduce this but I don't have the right setup
>> available, so this has to wait until the weekend when I have some more
> I was able to reproduce this issue: https server with basic
> authentication and KeepAlive Off, behind a http proxy.
> The scenario is exactly as how Ashish described it, the OPTIONS
> request is not sent over the ssl tunnel to the server, but directly to
> the proxy.
> The root cause is that the OPTIONS request, retried because of the
> authentication failure, was added in the queue for the new connection
> before the CONNECT request. When serf then opens a socket to connect
> to the proxy, it will first send the OPTIONS request.
> This issue has been fixed in r1991 on serf trunk, and I'll propose it
> for backport to serf 1.3.0.
Looking forward to see it backported.
> Thanks for the report Ashish!
“If 10 years from now, when you are doing something quick and dirty, you
suddenly visualize that I am looking over your shoulders and say to yourself,
"Dijkstra would not have liked this", well that would be enough immortality for
me.” (Edsger W. Dijkstra)
Sent from my Emacs
Received on 2013-07-03 17:35:49 CEST