You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2002/06/21 18:13:11 UTC
DO NOT REPLY [Bug 10128] -
1.3.26 (somebody updating bugzilla?): mod_proxy, no-cache and 304
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10128>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10128
1.3.26 (somebody updating bugzilla?): mod_proxy, no-cache and 304
------- Additional Comments From trawick@apache.org 2002-06-21 16:13 -------
Thanks for your report, especially for the patch. I hope the code issue is
resolved shortly.
I'm really sorry about the hard feelings you have regarding Apache developers
and the Apache development process, particularly with regard to problem
reports. I suspect that you may have unrealistic expectations about how Apache
is developed. We are all volunteers here, doing the best we can. It is
frustrating to follow these bug reports, many of which are for build problems
on machines that have screwy tool setups that we could never hope to
duplicate. Still more are from people who never respond to requests to test
patches or submit more information for diagnosis. And yet many PRs are
resolved on a regular basis. I'm quite sure that the delay
in handling your PR was due to a lack of appropriate knowledge among those
people who volunteer to follow the PRs and attempt to help the user community
through this channel. In many instances, the person encountering the problem
knows much more about it than we humble souls following the PRs. In cases like
this, the best way for the person encountering the problem to make progress is
to discuss the issue on one of the mailing lists or newsgroups and try to find
someone with the right skills to get involved.
Alternatively, there are various companies and perhaps individuals who are
willing to provide more tangible support for Apache or web servers based
directly on Apache. In case it is important to you, part of what you get when
you mail them the check is the ability to berate them until they fix whatever
problem you are encountering.
And as you have discovered, you are certainly empowered to work out a problem
yourself without involving any third parties. No Apache developer would deny
the fact that a great number of issues are resolved, with fixes contributed, by
the end users themselves. The important "product" we produce, extending beyond
a particular piece of downloadable software, is a framework for people to
contribute towards its continual improvement. Such contributions are well-
documented in the CHANGES files and are what makes Apache a reasonable solution
for many people.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org