Appendix C[ 281 ]Once the problem has been defined, the next step is describing how that problem can
be reproduced:
Calling http://subdomain.example.com/serverstatus yields a "404 File
Not Found".This will help whoever is looking at this problem to try to solve it. It ensures that there
is a non-working case that can be shown to be working once the problem is solved.
Next, it is helpful to describe the environment in which this problem was observed.
Some bugs only surface in certain operating systems or with a particular version of
a dependent library.
Any configuration files necessary to reproduce the problem should be included in the
report. If a file is found in the software archive, then a reference to that file is enough.
Read your bug report before sending it off. Often, you will find that some information
has been left out. Sometimes, you will find that you have even solved the problem
yourself, just by defining it clearly!
Summary
In this appendix, we learned a bit about the community behind NGINX. We saw
who the major players are and what resources are available online. We also got an
in-depth look at writing a bug report that should be helpful in finding a solution
to a problem.