Can digest auth be added to this module?

[mark-epstein]

caveats:

1. I don't 100% know what I'm talking about. Please correct me if I'm using the wrong terminology or just the wrong understanding of how things work.
2. I understand and accept that the generic modules are just for testing, that the best approach is to have a module specifically for each device out there. But I also believe that the community is best served by a triage mentality: you apply your resources where they are most needed first. I've barely heard of anyone using Marshall cameras let alone wanting to control them so they are probably way down on the priority list, so I'm willing to use the generic module until such time as a specific module would be written.

Marshall Electronics has a line of PTZ cameras for which they have recently released firmware that allows CGI commands to be sent to it over an http (port 80) connection. But in order to communicate with the camera requires Digest authentication.

I tried sending the credentials using Basic authentication - using the header input(JSON) field - but the camera just replied that it wanted Digest. Attached screenshot doesn't show the attempt to use Basic; just shows a successful communication using Chrome.

I'll create a separate request for a device-specific module, but I don't yet have permission to share the command set.

[mark-epstein]

I did submit a request for a Marshall-specific module.
I still think that handling this authentication would be a valuable addition to the generic module, for whatever comes down the line next

[otelom]

This would be nice to have, are you guys planning to add this?
@willosof @krocheck @JeffreyDavidsz @josephdadams

[philipcain]

Bump, this would be a valuable addition to the generic http module.

[mandurphy]

Just adding a +1 bump for digest authentication for the HTTP module as I also have a device that requires it that I'd love to control with Companion.