|Summary:||Add a debug line if Directory instruction provides an invalid path|
|Component:||Core||Assignee:||Apache HTTPD Bugs Mailing List <bugs>|
Description stephane.blondon 2019-01-16 18:04:44 UTC
`apachectl -t` should provide an info at 'debug' level if the path for <Directory> directive does not exist. For example, given <Directory /var/www/demo>, if /var/www/demo does not exist, `apachectl -t -e DEBUG` does not complain (tested with v.2.4.37). It would display something like AH00112 for DocumentRoot: 'Warning: DocumentRoot [/var/www/demo] does not exist' so it would be: 'Debug: Directory /var/www/demo does not exist'
Comment 1 mordax 2019-01-17 19:13:07 UTC
I'd like to work on this - however I am new to the project. Would you folks recommend this bug as something that a newcomer can tackle?
Comment 2 Christophe JAILLET 2019-01-17 21:29:38 UTC
Hi mordax, yes this looks like a good candidate to start with. - Should be easy enough to get fast and visible results - Low risk, just a debug message added - Helpful to spot potential configuration issues (typo, ...) In other work, perfect for a first try. You should work on the 'trunk' branch as any patch has to go there first. Do not hesitate to discuss on firstname.lastname@example.org for whatever help or explanation you need. If not already done, first download code via svn, configure your build environment, build from source. Once you can get your own build server, you can start to change/fix/improve things. Some docs are available for all that, but the new eye of a newcomer is always welcomed to improve our documentation. So whatever looks missing, unclear, spurious, not working, please report it. It will be appreciated. Welcome on board and happy hacking :)
Comment 3 Christophe JAILLET 2019-01-17 21:32:33 UTC
mordax: My comment #1 has not been mailed to you., so I've added you on the CC list of this bug so that you can receive any update.
Comment 4 mordax 2019-01-19 02:03:07 UTC
(In reply to Christophe JAILLET from comment #2) Hi Christophe, > Welcome on board and happy hacking :) Thanks for the warm welcome, I'm looking forward to helping out! I appreciate the clarification on the steps - I've been reading the docs but it's always nice to have confirmation that you've understood correctly. And thanks, I'll reach out for help if I need it. Out of curiousity, would you recommend the Apache IRC channel for quick questions, or is it less active than the mailing list? > Some docs are available for all that, but the new eye of a newcomer is > always welcomed to improve our documentation. Of course, speaking as a sad Windows developer, I'm no stranger to documentation improvements. ;) Happy to help out.
Comment 5 Christophe JAILLET 2019-01-19 06:52:19 UTC
(In reply to mordax from comment #4) > Out of curiousity, would you recommend the Apache IRC channel for quick > questions, or is it less active than the mailing list? IRC is obviously more reactive, ... but it depends of who is online. Mailing list is slower, ... but the audience is wider. Personally, I nearly never use IRC. Some others are always connected (even if not always behind their keyboard :) ). Try out and make your own opinion. I propose to you to switch to one (or both) of these 2 channels, in order not to hijack too much this report.
Comment 6 stephane.blondon 2019-01-19 14:07:27 UTC
I started to work on a patch after sending the bug report. Currently, I guess the patch should include a call to ap_log_error(APLOG_MARK, APLOG_DEB, ...) around line 2374 in core.c. (I used last archive of released apache to get a try). However, I don't plan to contribute more to Apache in the future. So if mordax wants that, I think it's better if he does the patch.
Comment 7 stephane.blondon 2019-01-19 14:15:59 UTC
I started to work on a patch after sending the bug report. Currently, I guess the patch should include a call to ap_log_error(APLOG_MARK, APLOG_DEB, ...) around line 2374 in core.c. (I used last archive of released apache to get a try). However, I don't plan to contribute more to Apache in the future. So if mordax wants that, I think it's better if he does the patch. Currently, I stopped to work on it to avoid duplicate efforts.
Comment 8 mordax 2019-02-01 21:01:33 UTC
Still gonna work on this bug, however my attempts at getting the server built using a x64 Windows machine alongside VS studio 2017 tooling has failed relatively miserably. I had a process for writing out potentially new documentation for it, but I'm most likely going to abandon in it favour of a Linux vm and just building it there. Unless there's a master who has it built and running perfectly from source on their Win machine in Apache?