Digest Authentication changes

[RogerHardiman]

1. pass the http 'request' to the Parent via the request listener 2) catch a new type of 'throw' with a HTTP Status Code, Header and Contents

[RogerHardiman]

Hi
I don't have permissions to write to the node-soap fork so have done a pull request.
However that is handy git push --set-upstream origin digest as it is worth explaining what I've changed.

ONVIF supports user authentication in the XML (called WS-Security) and also supports HTTP Digest Authentication at the HTTP level.
The problem I had was that I needed to see the HTTP Headers (WWW-Authentication / authorize) and return a HTTP 401 status code as part of the HTTP Digest implementation so I pass the HTTP Request object over to RPOS and RPOS can throw a new type of 'throw' with a HTTP Status Code.

I did try and implement HTTP Direct Authentication earlier in the HTTP Request processing but had issues where node-soap removes other 'listeners' to the http request event or found some http digest libraries too inflexible.

[BreeeZe]

Hi! Since this repo is an integral part of RPOS I added you as a collaborator 👍🏻