OCSP, it falls back to its own (if configured) stapling implementation.
3. mod_md registers itself at the core hooks for OCSP provisioning. Depending
on configuration, it will accept registrations of its own certificates only,
- all certficates or none.
+ all certificates or none.
[Stefan Eissing]
const md_t *md, struct md_pkey_spec_t *spec, apr_pool_t *p);
/**
- * Synchronise the give master mds with the store.
+ * Synchronize the given master mds with the store.
*/
apr_status_t md_reg_sync_start(md_reg_t *reg, apr_array_header_t *master_mds, apr_pool_t *p);
/* _________________________________________________________________
**
-** Certficate/Key Stuff
+** Certificate/Key Stuff
** _________________________________________________________________
*/
* called for both cases. */
char *modssl_bio_free_read(apr_pool_t *p, BIO *bio);
-/* Read a single certificate and its private key from the give string in PEM format.
+/* Read a single certificate and its private key from the given string in PEM format.
* If `key_pem` is NULL, it will expect the key in `cert_pem`.
*/
apr_status_t modssl_read_cert(apr_pool_t *p,
static int ssl_is_https(conn_rec *c)
{
- /* Someone retrieved the optional function., not knowning about the
- * new API. We redirect them to what they should have inoked. */
+ /* Someone retrieved the optional function., not knowing about the
+ * new API. We redirect them to what they should have invoked. */
return ap_ssl_conn_is_ssl(c);
}
conn_rec *c, request_rec *r,
const char *name)
{
- /* Someone retrieved the optional function., not knowning about the
- * new API. We redirect them to what they should have inoked. */
+ /* Someone retrieved the optional function., not knowing about the
+ * new API. We redirect them to what they should have invoked. */
return ap_ssl_var_lookup(p, s, c, r, name);
}