[PATCH] add our version to string to httpd banner
Before:
Server: Apache/2.0.54 (Unix) DAV/2 mod_perl/2.0.2-dev Perl/5.8.7
After:
Server: Apache/2.0.54 (Unix) DAV/2 mod_apreq/2.1.2-dev
mod_perl/2.0.2-dev Perl/5.8.7
[EMAIL PROTECTED] /usr/local/dev/repos/ASF/httpd/apreq/trunk svn diff
Index: module/apache/command.c
===
--- module/apache/command.c (revision 210049)
+++ module/apache/command.c (working copy)
@@ -18,6 +18,7 @@
#include apreq_util.h
#include apreq_module_apache.h
+#include apreq_version.h
#include httpd.h
#include http_log.h
@@ -152,6 +153,7 @@
apr_initialize();
apr_pool_create(p, NULL);
apreq_initialize(p);
+ap_add_version_component(p, apr_psprintf(p, mod_apreq/%s,
APREQ_VERSION_STRING));
ap_register_cleanup(sp, p, apreq_cleanup, apreq_cleanup);
}
Index: module/apache2/filter.c
===
--- module/apache2/filter.c (revision 210049)
+++ module/apache2/filter.c (working copy)
@@ -29,6 +29,7 @@
#include apreq_private_apache2.h
#include apreq_error.h
#include apreq_util.h
+#include apreq_version.h
static void *apreq_create_dir_config(apr_pool_t *p, char *d)
{
@@ -423,6 +424,8 @@
{
apr_status_t status;
+ap_add_version_component(p, apr_psprintf(p, mod_apreq/%s,
APREQ_VERSION_STRING));
+
status = apreq_post_initialize(p);
if (status != APR_SUCCESS) {
ap_log_error(APLOG_MARK, APLOG_STARTUP|APLOG_ERR, status,
base_server,
--
END
What doesn't kill us can only make us stronger.
Nothing is impossible.
Philip M. Gollucci ([EMAIL PROTECTED]) 301.254.5198
Consultant / http://p6m7g8.net/Resume/resume.shtml
Senior Developer / Liquidity Services, Inc.
http://www.liquidityservicesinc.com
http://www.liquidation.com
http://www.uksurplus.com
http://www.govliquidation.com
http://www.gowholesale.com
Re: APR::Request::Param::Table
Adam Prime [EMAIL PROTECTED] writes: Here's how i would have done what i'm trying to do in mp1. The docs say this interface is broken, but they aren't explaining to me very clearly what i'm supposed to do to get this sort of functionality in mp2 You can't do it anymore with apreq's 2.x API. This functionality was dropped with 2.05-dev, but the docs weren't updated properly to reflect the change. Sorry about that. -- Joe Schaefer
Re: [PATCH[ library/t/Makefile.am
Philip M. Gollucci [EMAIL PROTECTED] writes: P.S. whats needed for the TODO for dropping automake and using apr/httpd conf things. Hard work- lots of it, I'd suppose. It's prolly a lot easier for httpd to just extract our C files and incorporate those directly into their build system. -- Joe Schaefer
Re: [VOTE] mod_ftp for HTTP Server Project
Jeff McAdams wrote: I could easily see this resulting in FTPS support finally being available in open source. Not that I'm a big fan of FTPS in general, but not having an FTPS server available in the open source world is something of a gap that probably should be filled. I haven't checked how good they work personally, but there are several open source FTPS servers like proftpd and vsftpd: http://www.proftpd.org/ http://vsftpd.beasts.org/ Regards Rüdiger
Re: [VOTE] mod_ftp for HTTP Server Project
[EMAIL PROTECTED] wrote: I haven't checked how good they work personally, but there are several open source FTPS servers like proftpd and vsftpd: http://www.proftpd.org/ http://vsftpd.beasts.org/ Hrmm...ok...and we use vsftpd...interesting, I didn't realize it supported it. I do remember, now, why we don't support FTPS, and it wasn't because of the (perceived) lack of servers...our load-balancing system doesn't support it. Well, regardless...mod_ftp could lead to FTPS support in Apache, which could be a good thing in any case. :) -- Jeff McAdams They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin signature.asc Description: OpenPGP digital signature
mod_mbox user interface
Hi, As promised, here comes a description of my plans on mod_mbox new user interface. First of all, it is very important that mod_mbox works with all browsers (in the idea of Best viewed with all browsers). This is why I will distinguish two modes : - the classic, Javascript-less interface - the JS-powered AJAX browser. The homepage of a mailing list archive will display the list of available mailboxes (as it does now), and for each mailbox, it will propose something like this : July 2005Browse (242 messages) (or browse by date, author or thread) Each of the three bottom links (date, author, thread) are links to the simple interface. This line may be displayed smaller than the main link. There is not much to say about the classic interface. It's a kind of compatibility mode, and it will works exactly as the current version of mod_mbox : browse by date, author and thread, viewing individual message once at a time, etc. URIs for this mode are (base: /MM.mbox/) : /date /thread /author /message_id All these URIs reply with XHTML contents (or whatever output format we choose). The browser will be very different. After you've choosed the mailbox you want to browse, it will load a very simple XHTML page with an onLoad Javascript function, located at /MM.mbox/browser. This function will make a first request to grab the mailboxes list and display it in a sidebar on the left. Each mailbox has is linked to its corresponding browsing interface, and the current one is highlighted. Then, it will make another request to grab the message list, and display it in the main part of the page, in the default sort format : threads. +---+ ++ | Box list | | Message list Threads | Authors | Date | +---+ +--+--+--+ | Jul 2005 242 | | Maxime Petazzoni | mod_mbox | Jun 26th | |*Jun 2005**561*| | Paul Querna | Re: mod_mbox | Jun 27th | | May 2005 478 | | In the message list box header, links for changing message list sort order. These links do not make any request to the server, the Javascript will do the job. When the user clicks on a message, the message list collapse to a ten lines message context, and a new box appears under the message list to display the mail. Mail contents are fetched by a Javascript request. The current message is highlighted in the message list. In the message view box header, links for next and previous message (in current sort order), and a 'X' to close the message, and re-expand the message list. This features requires some backend URIs that mod_mbox must handle. These URIs will be answered with XML contents. They will be (still based on: /MM.mbox/) : - Box list : /ajax/boxlist Reply: mailboxes mbox year=2005 month=07 msgs=242 / mbox year=2005 month=06 msgs=561 / !-- the rest ... -- /mailboxes The year split I added recently will be deleted since it's not a good XML structuration. - Message list : /ajax/msglist Reply: messages thread mail id=... linked=0 from[EMAIL PROTECTED]/from strfrom Maxime Petazzoni lt;[EMAIL PROTECTED]gt; /strfrom subjectmod_mbox/subject dateSun, 26 Jun 2005 17:42:42/date /mail thread mail id=... linked=1 ... /mail /thread /thread /messages The linked parameter is set to 0 if the message comes from another mailbox, but the replies are in the current one. In this example, the current mailbox could be July 2005, and the second mail replies to a mail from June 2005. - Message : /ajax/message_id mail from[EMAIL PROTECTED]/from strfrom Maxime Petazzoni lt;[EMAIL PROTECTED]gt; /strfrom subjectmod_mbox/subject dateSun, 26 Jun 2005 17:42:42/date smime smime id=1 attach id=1 type=text/plain name=Message / attach id=2 type=text/plain name=mod_mbox.patch / /smine attach id=2 type=application/pgp-signature name=OpenPGP Signature / /attachments contents Hi, This is a signed S/MIME mail with an attached patch ! - Sam /contents /mail Well, I think that's all I need to say on the browser. I know this may not be perfect, so feel free to comment and criticize, especially the XML replies. - Sam -- Maxime Petazzoni (http://www.bulix.org) -- gone crazy, back soon. leave message. signature.asc Description: Digital signature
Re: 1.3 and 2.0 releases?
William A. Rowe, Jr. wrote: I know a few folks were expecting this note last Friday... here's the scoop. Jeff's patch to 2.0 was lovely. What's not lovely is that the chunked request processing has been hosed since at least 2.0.54. As much as I'd rather just commit his patch and release, there is a deeper problem going on that I'm investigating. Some of it seems to have to do with trailers and expected CRLF values. I'm not certain the 2.0 filters are doing the right thing. It seems that the 2.1 filters are correct. Until I can get 2.0 to serve all my test cases, it's somewhat pointless to push out a release. On the 1.3 side, I only see one remaining issue undisclosed which I'll commit on Monday and push that out the door. I've asked for votes on a few patches which are falling on deaf ears. If you are a 1.3 user, please review. You know, we should be creating a branch of the 1.3/2.0/2.1 tree and fold the patches directly into them. Much easier for people to then try them out, update as needed, etc... Now that we have SVN, we should start using it, meaning that in special cases like this, passing patches back and forth is kind of inefficient. -- === Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/ Sith happens - Yoda
Re: mod_mbox user interface
Hi again, The homepage of a mailing list archive will display the list of available mailboxes (as it does now), and for each mailbox, it will propose something like this : July 2005Browse (242 messages) (or browse by date, author or thread) Each of the three bottom links (date, author, thread) are links to the simple interface. This line may be displayed smaller than the main link. After a quick chat with chipig on #apache-modules, we found a better solution : these links will be build via Javascript. If the browser can do Javascript, the 'Browse' link will be displayed (and the three others in small under it). Otherwise, only the three browsing method links will be shown. +---+ ++ | Box list | | Message list Threads | Authors | Date | +---+ +--+--+--+ | Jul 2005 242 | | Maxime Petazzoni | mod_mbox | Jun 26th | |*Jun 2005**561*| | Paul Querna | Re: mod_mbox | Jun 27th | | May 2005 478 | | I've made a small and simple mockup in order to give a better idea of what it could look like. You can find it at http://blog.bulix.org/pics/soc-2005/mockup.jpg - Sam -- Maxime Petazzoni (http://www.bulix.org) -- gone crazy, back soon. leave message. signature.asc Description: Digital signature
mod-cache-requestor plan
Hi All, I am a newbie. I am going to work on mod-cache and a new module mod-cache-requester as a part of Soc program. Small description of the module is as follows. When the page expires from the cache, it is removed from cache and thus next request has to wait until that page is reloaded by the back-end server. But if we add one more module which re-request the soon-to-expire pages, in that case such pages wont be removed from the cache and thus would reduce the response time. Here is the overview of how am I planning to implement it. 1. when a page is requested and it exists in the cache, mod_cache checks the expiry time of the page. 2. If (expiry time – current time) Some_Constant_Value, then mod-cache notifies mod_cache_requester about this page. This communication between mod_cache and mod_cache_requester should incur least overhead as this would affect current request's response time. 3. mod_cache_requester will re-request the page which is soon-to-expire. Each such request is done through separate thread so that multiple pages could be re-requested simultaneously. This request would force the server to reload the content of the page into the cache even if it is already there. (this would reset the expiry time of the page and thus it would be able to stay in the cache for longer duration.) Please let me know what you think about this module. Also I have some questions and your help would be really useful. 1.what would be the best way for communication between mod_cache and mod_cache_requester. I believe that keeping mod_cache_requester in a separate thread would be the best way. 2.How should the mod_cache_requester send the re-request to the main server. I believe that sending it as if the request has come from the some client would be the best way to implement. But we need to attach some special status with this request so that cache_lookup is bypassed and output_filter is not added as we dont need to stream the output. 3.Other than these questions, any suggestion/correction is welcome. Any pointers to the details of related modules( mod-cache, communication between mod-cache and backend server) would be helpful too. Thanks, Parin.
