www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From oneway <oneway_...@yahoo.com>
Subject other/8800: Could get HTTPS working with Apache 2.0.28
Date Mon, 19 Nov 2001 02:22:03 GMT

>Number:         8800
>Category:       other
>Synopsis:       Could get HTTPS working with Apache 2.0.28
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sun Nov 18 18:30:01 PST 2001
>Originator:     oneway_111@yahoo.com
>Release:        2.0.28
RH 7.2
Apache 2.0.28 beta
1) "make certificate" does not appear to be a valid build option for apache 2.0.28
2) after generating a test certificate using OpenSSL "make_dummy_cert" utility and changing
.../conf/ssl.conf file apache still does not listen on port 443
1) follow instuctions on http://httpd.apache.org/docs-2.0/ssl/ssl_faq.html#ToC27
2) try to use https:// with apache 2.0.28
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]

View raw message