What should i do to bring attention to the bug?

[Kevac Marko <mk...@gmail.com>]

Hello.

What can i possibly do and what i should do to bring some attention to
opened bug? Patch attached, so i need some review and testing,
something...
I would really like to see this feature in httpd.

Bug i am talking about is here:
https://issues.apache.org/bugzilla/show_bug.cgi?id=45456

-- 
С уважением, Кевац Марко
Sincerely yours, Kevac Marko

Re: What should i do to bring attention to the bug?

["William A. Rowe, Jr." <wr...@rowe-clan.net>]

Kevac Marko wrote:
> 
> What can i possibly do and what i should do to bring some attention to
> opened bug?

Posting to the dev list is a good thing.  modules-dev is not the dev list,
this list is for discussion of third party module development.  A number
of the core developers follow this list, but certainly not all, and perhaps
not the ones you need to excite about this proposed feature.

If this were an API change, modules-dev would be a good place to start
(to get other module developers excited about the suggestion).  But since
this is a config/userland change, dev@httpd.apache.org is the way to go.

> Patch attached, so i need some review and testing, something...
> I would really like to see this feature in httpd.

One thing patch authors can do is to integrate the testing of their patch
(be it a bug fix or proof of successful new feature), the framework lives in

http://svn.apache.org/viewvc/httpd/test/framework/trunk/

It's not mandatory, but might help a developer less familiar with the
internals of that code to prove to themselves that the suggested patch
is right.

> Bug i am talking about is here:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=45456