You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that some LCP/LSD HTTP requests are created in the r2-lcp-js package independently of Thorium's own code (i.e. LSD fetch, and register, return, renew):
I agree with closing this issue for now. There was one feature request from a user (technical person) to enable the configuration inside Thorium of HTTP proxy (which we could technically implement via an Agent in our NodeFetch HTTP client).
However this does not seem to be a high priority (no further feedback).
thorium-reader/package.json
Line 253 in e518c1d
https://github.com/edrlab/thorium-reader/tree/develop/src/main/network
=>
https://github.com/node-fetch/node-fetch#custom-agent
Suggestions:
https://github.com/insightfuls/better-https-proxy-agent
https://github.com/TooTallNate/node-https-proxy-agent
https://github.com/snoguchi/node-fetch-with-proxy
https://github.com/zjael/simple-proxy-agent
Note that some LCP/LSD HTTP requests are created in the
r2-lcp-js
package independently of Thorium's own code (i.e. LSD fetch, and register, return, renew):https://github.com/readium/r2-lcp-js/tree/develop/src/lsd
The text was updated successfully, but these errors were encountered: