2.1.6 on Friday
I would like to roll another alpha on this Friday, June 24th. I hope to resolve these issues that blocked 2.1.5 from going out: 1) Compile on Win32. 2) Proper use of strcasecmp to check for identity encoding. (d'oh) 3) Fix any cases where the protocol is not set/NULL. Anything else anyone wants to get in? Thanks, Paul
What's important to an Apache protocol handler?
Hi, All: It's known that somebody have developed modules to support other protocols in httpd, such as ftp, pop3. I wonder whether these modules are in use actually or just proof-of-concepts now? Given you are the network manager, do you consider to use them? (more important)why or why not? Obviously, it's better to provide more useful features than to re-develop what has been done by others. I may do the similar thing, developing a smtp handler, in these days. In order to attract the users, I plan to focus on providing some mechanism about anti-spam, such as register source of spam by the mail receiver reports automatically. Any technical/functional advices and disscussions would be greatly appreciated. -- Luo Gang
Re: apache developers documentation!!!
Title: Re: apache developers documentation!!! On 6/21/05 5:29 PM, "Nick Kew" <[EMAIL PROTECTED]> wrote: > (2) http://www.apachecon.com/ - come to our module developers tutorial > and other talks. When will there be another apachecon US? -- Brian Akins Lead Systems Engineer CNN Internet Technologies
Apache Webserver Usage Survey
Hi. I am conducting a survey about what users want out of a webserver and how the Apache webserver ranks as far as fulfilling those needs. In order to get a better understanding of it, I thought I would ask you guys what was important to you. The survey should take about 10-15 minutes to complete. http://survey.zilbo.com/dev.survey I wish I could say there was a prize being given away if you fill it out, but there isn't.. This is 'opensource' research.. I don't have a marketing budget ;-) Regards Ian Holsman [EMAIL PROTECTED]
Re: Reward SSL and IE
Title: Re: Reward SSL and IE The problem was actual a certificate. The key was generated by a newer version of openssl than we normally use (0.9.6 vs 0.9.7)) and somehow that translated to a cert from Verisign that did not work on Win98 and IE. Strange. -- Brian Akins Lead Systems Engineer CNN Internet Technologies
Re: Reward SSL and IE
At 07:30 PM 6/20/2005, Akins, Brian wrote: >[Mon Jun 20 20:23:23 2005] [debug] ssl_engine_io.c(1522): OpenSSL: I/O >error, 11 bytes expected to read on BIO#87b01f8 [mem: 880daa8] >[Mon Jun 20 20:23:23 2005] [debug] ssl_engine_kernel.c(1813): OpenSSL: Exit: >error in SSLv2/v3 read client hello A[Mon Jun 20 20:23:23 2005] [info] >(70014)End of file found: SSL handshake interrupted by system [Hint: Stop >button pressed in browser?!] This looks -very- familiar. Which version of OpenSSL? Bill
Re: Reward SSL and IE
At 02:27 PM 6/21/2005, Jeff White wrote: >Is one's latest web server compiled with >the Microsoft designed (for any OS) >Safer CRT libraries? There's nothing "Safe" about the standard C library or Microsoft's library, except how they are used. Most all necessary behaviors (buffer length args to avoid overruns, etc) are now part of all modern c libraries, in a posix compliant flavors. Sadly, and par for course, Microsoft is disinterested in any portability. Therefore relatively trivial conventions become convoluted as Microsoft pollutes the namespace with their own proprietary inventions. In fact the HTTP project believes in certain typical C library behaviors as much safer than Microsoft's concept of "safety". For example, dereferencing a NULL pointer is something that can happen throughout the httpd server code. In every case, a non- NULL value is an unexpected fatal condition, and every platform will fault when that condition occurs. Is it "better" than wordy error messages and clean failures? That's left as an exercise to the developer. But in this team's opinion, allowing the compiler and library to do exactly what they were designed to do, and break upon hitting these exceptions, ensures that no further processing occurs for broken code. Since there is no error in processing this request, but it happens to be a logic error in SSL handshaking, I doubt either fiddler or ethereal will help any for the casual developer. Certainly the 'safe' libraries would do little to nothing. Bill
Re: apache developers documentation!!!
On Tuesday 21 June 2005 21:32, arebassa arebassa wrote: > Hi all, > > I'm very newbie to apache development and I'd like to know more > about it. Is there any documentation about the functionalities of the > differents parts of code? how the code is structured? what is a bucket > brigade?... I have started looking at the documentation at > http://docx.webperf.org/index.html but I wander if there is any > documentation more focused on newbies. If I might blow my own trumpet:- (1) http://www.apachetutor.org/ - go to the Developer tutorials (which is the only section of the site with any contents). (2) http://www.apachecon.com/ - come to our module developers tutorial and other talks. -- Nick Kew
apache developers documentation!!!
Hi all, I'm very newbie to apache development and I'd like to know more about it. Is there any documentation about the functionalities of the differents parts of code? how the code is structured? what is a bucket brigade?... I have started looking at the documentation at http://docx.webperf.org/index.html but I wander if there is any documentation more focused on newbies. Thank you very much for your help and apologize if this question has been already made thousands of times. -- Arnau
Re: Reward SSL and IE
From: "Akins, Brian" definitively help use with a mod_ssl (Apache 2.0.54) and IE issue. As posted all the time on the Apache users list: MSN Search http://search.msn.com/results.aspx?q=fiddler+http http://search.msn.com/results.aspx?q=%27IEBlog+A+HTTP+Detective+Story%27 What is Fiddler? http://weblogs.asp.net/ssadasivuni/archive/2005/06/08/410834.aspx Is one's latest web server compiled with the Microsoft designed (for any OS) Safer CRT libraries? Jeff
Re: Bugzilla: when is a bug FIXED?
On Tuesday 21 June 2005 18:38, William A. Rowe, Jr. wrote: > At 12:31 PM 6/21/2005, Nick Kew wrote: > >On Tuesday 21 June 2005 10:46, [EMAIL PROTECTED] wrote: > >> if we have set of directories with only some of them protected with > >> password these protected entries are not shown. > > > >This got marked as a duplicate of PR10575, which is Closed/Fixed because > > it got fixed in 2.1/HEAD. But it's *not* fixed in the stable version, > > 2.0, which is what the report was about! > > There is a FixedInTrunk keyword now, which should probably apply > to any bug not backported to 2.0. That would imply that such bugs MUST remain OPEN, so that searches for bugs applicable to released versions will find them. The bug in question - among others - was marked FIXED. -- Nick Kew
Re: Bugzilla: when is a bug FIXED?
At 12:31 PM 6/21/2005, Nick Kew wrote: >On Tuesday 21 June 2005 10:46, [EMAIL PROTECTED] wrote: > >> if we have set of directories with only some of them protected with password >> these protected entries are not shown. > >This got marked as a duplicate of PR10575, which is Closed/Fixed because it >got fixed in 2.1/HEAD. But it's *not* fixed in the stable version, 2.0, which >is what the report was about! There is a FixedInTrunk keyword now, which should probably apply to any bug not backported to 2.0. Bill
Bugzilla: when is a bug FIXED?
On Tuesday 21 June 2005 10:46, [EMAIL PROTECTED] wrote: > if we have set of directories with only some of them protected with password > these protected entries are not shown. This got marked as a duplicate of PR10575, which is Closed/Fixed because it got fixed in 2.1/HEAD. But it's *not* fixed in the stable version, 2.0, which is what the report was about! We have quite a lot of bugs like that. Perhaps we need a "provisionally fixed" status in Bugzilla, to denote a bug that's fixed in DEV but not in the current release version? That way we can legitimately advise people to include provisionally-fixed bugs in their search before submitting a new report. -- Nick Kew
Re: svn commit: r191647 - /httpd/httpd/trunk/server/util_script.c
Jeff Trawick wrote: > On 6/21/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > >>Author: niq >>Date: Tue Jun 21 03:53:00 2005 >>New Revision: 191647 >> >>URL: http://svn.apache.org/viewcvs?rev=191647&view=rev >>Log: >>PR 10755: committing patch from Christian Schubert > > > Here is the normal form of a commit log: Bah. I mistyped PR 10775. Corrected now - thanks. -- Nick Kew
Re: svn commit: r191647 - /httpd/httpd/trunk/server/util_script.c
On 6/21/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Author: niq > Date: Tue Jun 21 03:53:00 2005 > New Revision: 191647 > > URL: http://svn.apache.org/viewcvs?rev=191647&view=rev > Log: > PR 10755: committing patch from Christian Schubert Here is the normal form of a commit log: PR:10755 Submitted by: Christian Schubert Reviewed by: niq If the change fixes a bug that somebody else might encounter, you need to add a CHANGES entry as well.
Re: Removing AddOutputFilterByType
On Tuesday 21 June 2005 06:10, Astrid Keßler wrote: > at Montag, 20. Juni 2005, Nick Kew wrote: > > Hmmm. Is it better to have a UI that's openly a little more complex but > > works as documented, or one that appears simple but has lots of > > gotchas lurking in ambush? I guess that's an argument for mod_filter > > implementing AddOutputFilterByType. > > First, it's an argument to improve the docs ;) Not sure about that. Full documentation for AddOutputFilterByType could become quite mindboggling. The gotcha that generates most questions is "doesn't work at all in [various situations, notably a proxy]". ISTR that *is* documented somewhere, but people don't notice because it's unintuitive. Add the *ordering* issue (always comes *after* filters configured with other directives), and it's already more complex to get the mind around than mod_filter. Now add the complex interactions that happen in setups involving more than module, or even within a single module (c.f. http://issues.apache.org/bugzilla/show_bug.cgi?id=33499 ) and it's not IMO something that can be documented adequately without extensive self-defeating reference to the code itself. -- Nick Kew
