On Mon, Jan 18, 1999, Mark Dedlow wrote:
I've been running mod_ssl-2.1.0-1.3.3 for months without
a problem and using my own Auth handler ona high port. Now
I'm trying to run it in on port 443, and if I connect
via https:/host:443/ it works fine, but https:/host/
(no explicit port), NS
Dear all,
I've asked that question few days ago and didn't get an answer... I can
understand that my question is more linked to the ssleay layer and not
really to the mod-ssl but if It is impossible to create a 40 bits csr,
and if someone knows it, I'll really be glad to have that answer (I'm
kbg wrote:
Dear all,
I've asked that question few days ago and didn't get an answer... I can
understand that my question is more linked to the ssleay layer and not
really to the mod-ssl but if It is impossible to create a 40 bits csr,
and if someone knows it, I'll really be glad to have
Ralf,
On Mon, Jan 18, 1999, Mark Dedlow wrote:
I've been running mod_ssl-2.1.0-1.3.3 for months without
a problem and using my own Auth handler ona high port. Now
I'm trying to run it in on port 443, and if I connect
via https:/host:443/ it works fine, but https:/host/
(no
On Tue, Jan 19, 1999, James H.G. Redekop wrote:
I am having trouble getting mod_ssl to behave for a customer. It
compiled beautifully and everything, but now that it's up and running
it is rejecting all attempts at a connection with this error:
[Tue Jan 19 12:57:54 1999] [error] mod_ssl:
Ralf S. Engelschall wrote:
I'm not sure where the SSLeay library error would be found.
Usually directly following this error message. But there
are some cases inside SSLeay where no error message is set.
I figured as much. Ah well.
Usually it doesn't matter where it was generated,
