Default implementation in Signer triat uses hardcoded HTTP Resolver instead of the resolver on the Context

[duggaraju]

Component

c2pa-rs

If Other, please specify

No response

Version

0.84.0

Platform

Linux

What happened?

The default implementation of send_timestamp_request() in signer trait uses a hardcoded Resolver instead of using the context resolver. which means

1. You can't build with http disabled even if you implement your own http resolver.
2. The resolver set in the Context is used by builder but not by the timestamp request.

What did you expect to happen?

Ideally the API should take the context as a parameter which is passed from the builder and use the resolver from the context always.

[duggaraju]

Signer APIS should take Context as an argument to both support cancellation as well as http resolver.

[github-jira-sync-bot]

❌ Something went wrong. Cannot create Jira issue.