On Oct 12, 2011, at 1:10 AM, Tomas Kuliavas wrote:
>>
> Your error message says different thing. For some reason software tries to
> connect to http-over-ssl on 80 port.
>
>
I spent time in Apache working on vhost configuration and redirects
after a couple of days tweaking I have all browsers
JasonHirsh wrote:
>
>>>
>>
>> If you have HTTP-over-SSL service on 80 port, users connect to it with
>> "https://hostname:80";. If you use proper HTTP-over-SSL port, they connect
>> to "https://hostname";. No port numbers visible and URL is nicer.
>>
>>>
>
> the correct install works with h
>>
>
> If you have HTTP-over-SSL service on 80 port, users connect to it with
> "https://hostname:80";. If you use proper HTTP-over-SSL port, they connect
> to "https://hostname";. No port numbers visible and URL is nicer.
>
>>
the correct install works with https://hostname
>
> My tests sh
2011.10.11 19:50 jason hirsh rašė:
>>>
>>>
>> http-over-ssl on 80 port. Why are you doing it? What's wrong with basic
>> https://hostname/ and why do you want to show port numbers to end users.
>> It
>> can also be the cause of your secure cookie failure.
>
> OK i had just installed HTTPS support
>>
>>
> http-over-ssl on 80 port. Why are you doing it? What's wrong with basic
> https://hostname/ and why do you want to show port numbers to end users. It
> can also be the cause of your secure cookie failure.
OK i had just installed HTTPS support in prep for SM.. although I do not
remember
JasonHirsh wrote:
>
> Using Freebsd 8.0m Apache 22 with mod ssl, Dovecot and Postfix
>
> I have gotten SM up but I am find that after I compose a messsage and go
> to send it I get a different error in each of the three browsers I have
> tested
>
> In Firefox the message is send and I get
