It could happen that when several keys produces the same hash that
find_node was not trying hard enough to traverse the rb tree.
Thanks to Markus Doppelbauer for his detailed bug report and test case.

Signed-off-by: Brice Figureau <brice@daysofwonder.com>

Added an 'upload_progress_jsonp_output' directive that sets templates that work with jsonp.
Make jsonp parameter name configurable with the 'upload_progress_jsonp_parameter' directive.

Some uninitialized memory could lead to non array allocation in scripts,
leading to a segfault when reloading nginx.

Signed-off-by: Brice Figureau <brice@daysofwonder.com>

It was impossible to inherit the templates from an higher config level,
because the templates were overwritten when the config were merged.

Signed-off-by: Brice Figureau <brice@daysofwonder.com>

* global templates were not inited before their use
* relying on unpushed array made nelts == 0 and no array use
* code deduplication when initializing global templates

Signed-off-by: Brice Figureau <brice@daysofwonder.com>

This could happen with the upload module if for a reason the upload
is aborted. In this case an internal redirect is done, but the request
still contains our read even handler.
Unfortunately the request args are nullified before calling this read
even handler. So we were crashing because we didn't check for id==null.
This patch fixes this issue.

Signed-off-by: Brice Figureau <brice@daysofwonder.com>

When we clean a node, we ask nginx to free the memory. On some
platform or no load there were great chance the memory wasn't
reused for something else.
With high load and on FreeBSD, the memory seems to be reused
immediatly and we jump in the middle of f*****g nowhere, and
we crash.

Thanks to Vladimir Getmanshchuk for his bug report.

Signed-off-by: Brice Figureau <brice@daysofwonder.com>

This was due by reusing slabs from a terminated upload without reseting the
various parameters including the done parameter.

 * Added a content handler that overrides the original handler (but calls it). It is
used to add our own read_event_handler.

 * Implemented a read_event_handler that calls the original handler, and store the rest/content_length in our
own node.

 * modified the different handlers to use the new node fields

* added new CHANGES
* support for lowercase or mixed case X-Progress-ID header or parameter (fixes IE lowercasing headers)
* report original HTTP error code in probe in case of upload error
* fix crash reported by Michal Drapiewski

This version contains:
 * new timeout to remember connections after they are finished to be able
 to report termination on this connection to upload progress probes

 * handling of HTTP error 413 (request entity too large)

Addition of a header filter to track HTTP errors and return
the right status to upload progress probes.

This timer help us track finished connections and still report the status to progress probe.

* Added header filter to track 413 errors (not working atm)

 * First version