[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: A question abort port number problem of apache+ssl

From: Josh Gilkerson <jwg_at_google.com>
Date: 2007-06-04 18:55:47 CEST

On 6/4/07, Peter <smile_face@21cn.com> wrote:
> Hi,
>
> I have encountered a problem about the SSL usage.
>
> When set the apache's port number to 80, access repos by "https://192.168.1.11/xxx/yyy"

This isn't contacting port 80, its contacting the default https port, 443.

> suss. But when set the apache's port number to 8000, access repos by
> "https://192.168.1.11:8000/xxx/yyy" failed.

By setting apache's port number to 8000, you are probably setting the
apache http server to 8000. https is still listening on 443

> The error message are:
>
> Error: PROPFIND request failed on '/svn/market/trunk'
> Error: PROPFIND of '/svn/market/trunk': SSL negotiation failed: SSL error: unknown protocol (https://192.168.1.11:8000)

Trying to talk ssl to a non-ssl server port.

> when access the repos by "http://192.168.1.11:8000/svn/yyy:8000", everything seem ok.

notice the http, not https. The reason this works and not the previous
is the http/https, not the extra :8000 on the end.

> Why? If the port number 80 (80->443) is the SSL + apache required?

-- 
Josh Gilkerson
Software Engineer
Google, Inc
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 4 18:56:27 2007

This is an archived mail posted to the Subversion Users mailing list.