On Tue, Aug 14, 2012 at 1:10 AM, Philip Martin
wrote:
> Johan Corveleyn writes:
>
>> I tried all I can think of for configuring Apache. Pf.
>
> Do you have an explicit ServerName? Are you using VirtualHost? Can you
> connect using 1.7/neon? Can you connect using a browser?
Explicit Server
Johan Corveleyn writes:
> I tried all I can think of for configuring Apache. Pf.
Do you have an explicit ServerName? Are you using VirtualHost? Can you
connect using 1.7/neon? Can you connect using a browser?
Here is the complete Apache config file generated by davautocheck.sh:
LoadModu
On Mon, Aug 13, 2012 at 3:27 PM, Philip Martin
wrote:
> Philip Martin writes:
>
>> Johan Corveleyn writes:
>>
>>> wrote:
Me. subversion/tests/cmdline/davautocheck.sh does the relevant magic to
setup Apache if one uses:
make davautocheck USE_SSL=1
>>>
>>> Nice. I made a c
I considered generating the certificate but I am wary of draining the
system entropy. I don't know how much entropy generating an SSL
certificate requires but the testsuite doesn't need a high quality
certificate and it should avoid using entropy if possible. So I
embedded a pre-generated certifi
Neon's test suite has some logic in it to generate certificates. We
should probably do something similar for this.
Side note: If someone implements it just please don't do what neon
does and depend on the Gnu specific flag '-d' to the date command to
figure out the right timestamp to set on the
Philip Martin writes:
> Johan Corveleyn writes:
>
>> wrote:
>>> Me. subversion/tests/cmdline/davautocheck.sh does the relevant magic to
>>> setup Apache if one uses:
>>>
>>>make davautocheck USE_SSL=1
>>
>> Nice. I made a change (locally) to win-tests.py to also pass this
>> option, but it
Johan Corveleyn writes:
> wrote:
>> Me. subversion/tests/cmdline/davautocheck.sh does the relevant magic to
>> setup Apache if one uses:
>>
>>make davautocheck USE_SSL=1
>
> Nice. I made a change (locally) to win-tests.py to also pass this
> option, but it doesn't seem to work properly. I c
On Mon, Aug 13, 2012 at 9:28 AM, Philip Martin
wrote:
> Daniel Shahaf writes:
>
>> Johan Corveleyn wrote on Sat, Aug 11, 2012 at 22:11:22 +0200:
>>>
>>> Okay, I see there is an --ssl-cert option in svntest/main.py which
>>> does the necessary stuff. It's just not exposed through win-tests.py.
>>
Daniel Shahaf writes:
> Johan Corveleyn wrote on Sat, Aug 11, 2012 at 22:11:22 +0200:
>>
>> Okay, I see there is an --ssl-cert option in svntest/main.py which
>> does the necessary stuff. It's just not exposed through win-tests.py.
>
> Someone must have added it while I wasn't looking...
Me. s
Johan Corveleyn wrote on Sat, Aug 11, 2012 at 22:11:22 +0200:
> On Sat, Aug 11, 2012 at 8:54 PM, Daniel Shahaf
> wrote:
> > Johan Corveleyn wrote on Sat, Aug 11, 2012 at 10:25:02 +0200:
> >> Trying to further pin down issue #4174 [1], which only occurs with
> >> serf over https (and only on Windo
On Sat, Aug 11, 2012 at 8:54 PM, Daniel Shahaf wrote:
> Johan Corveleyn wrote on Sat, Aug 11, 2012 at 10:25:02 +0200:
>> Trying to further pin down issue #4174 [1], which only occurs with
>> serf over https (and only on Windows clients I think), I'd like to try
>> running the test-suite over https
Johan Corveleyn wrote on Sat, Aug 11, 2012 at 10:25:02 +0200:
> Trying to further pin down issue #4174 [1], which only occurs with
> serf over https (and only on Windows clients I think), I'd like to try
> running the test-suite over https. Is there any documentation on that?
> I looked in the comm
Trying to further pin down issue #4174 [1], which only occurs with
serf over https (and only on Windows clients I think), I'd like to try
running the test-suite over https. Is there any documentation on that?
I looked in the community guide, in subversion/tests/README and in
subversion/tests/cmdlin
13 matches
Mail list logo
