You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by "MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1)" <ma...@hp.com> on 2001/09/07 02:30:05 UTC
[PATCH] RE: [STATUS] (httpd-2.0) Wed Sep 5 23:45:09 EDT 2001
Hi,
I was wondering if somebody could update the status of mod_ssl in
the STATUS file. I'm providing my inputs - but if you have a more
appropriate comment, please go ahead and update it.
Thanks
-Madhu
Index: STATUS
===================================================================
RCS file: /home/cvspublic/httpd-2.0/STATUS,v
retrieving revision 1.283
diff -u -r1.283 STATUS
--- STATUS 2001/09/06 15:04:01 1.283
+++ STATUS 2001/09/06 22:17:02
@@ -112,29 +112,15 @@
* Port of mod_ssl to Apache 2.0:
- The current porting state is summarized in modules/ssl/README. The
next
- step is to figure out how the old three configuration contexts
(global,
- per-server, per-directory) can be ported to Apache 2.0 (especially
the
- global context which has to survive server restarts RSE still does
not
- know how to port). Then the remaining source files (which depend on
the
- configuration contexts) which are still tagged with "-" in
- modules/ssl/README can be ported.
+ The current porting state is summarized in modules/ssl/README. The
+ remaining work include :
+ (1) stablize the SSL filter logic
+ (2) Enable the various SSL caching mechanisms (shmcb, shmht)
+ (3) Enable SSL extentions
+ (4) Try to seperate the https filter logic from mod_ssl -
+ This is to facilitate other modules to use the https filter or
the
+ mod_ssl logic or both as required.
- One more thing to figure out is how and when mod_ssl can provide the
- interactive pass phrase dialog (in Apache 1.3 it used the first init
- round [where tty was still not detached] and skipped the second init
- round [where it was already detached]). Apache 2.0 requires (or
already
- has?) an official hook where such tty-dialogs can be performed.
-
- RSE is on holiday until June 11th, 2001. After this he starts
- working on mod_ssl again and tries to make mod_ssl running inside
- Apache 2.0 by end of June. If anyone wants to help making mod_ssl
- running in the meantime, feel free to make your hands dirty inside
- modules/ssl/. Do whatever you think is appropriate to get it
- running. I've no objections of any kind, except: just do not
- remove any old functionality. Keep everything, even if it needs
- #if 0...endif wrapped to not make trouble for you.
-
* Performance: Get the SINGLE_LISTEN_UNSERIALIZED_ACCEPT
optimization working in threaded. prefork's new design for how
to notice data on the pod should be sufficient.