We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is our 40-seconds timeout being set and used properly?
See discussion: #1007 (comment)
We are passing a timeout value of 40 seconds from the client to the SDK, which passes that value in the request JSON to securedrop-proxy We are actually not passing that timeout to securedrop-proxy to the current implementation. We are just using it to timeout the qrexec process command we are running in the sd-app vm, https://github.com/freedomofpress/securedrop-sdk/blob/master/sdclientapi/__init__.py#L64
We are passing a timeout value of 40 seconds from the client to the SDK, which passes that value in the request JSON to securedrop-proxy
We are actually not passing that timeout to securedrop-proxy to the current implementation. We are just using it to timeout the qrexec process command we are running in the sd-app vm, https://github.com/freedomofpress/securedrop-sdk/blob/master/sdclientapi/__init__.py#L64
securedrop-proxy
qrexec
sd-app
The text was updated successfully, but these errors were encountered:
this is a duplicate of freedomofpress/securedrop-proxy#145
Sorry, something went wrong.
No branches or pull requests
Description
Is our 40-seconds timeout being set and used properly?
See discussion: #1007 (comment)
The text was updated successfully, but these errors were encountered: