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
I came across the following use case: I deal with 3rd party HTTPS client that is broken. It does not establish a TLS connection. I would like to check why - either it's a matter of cipher suites or TLS versions. However, I'm unable to retrieve the body (since it's client beyond my control)
Therefore it would be nice to have API that could store the TLS report and this report could be retrievable by some kind of ID.
Something like POST /create-link ( generated link in body response or header)
Then I would be able to feed the client with a generated link.
After making a request on the generated link I would be able to retrieve the report - eg. GET /generated-link/report
The text was updated successfully, but these errors were encountered:
I came across the following use case: I deal with 3rd party HTTPS client that is broken. It does not establish a TLS connection. I would like to check why - either it's a matter of cipher suites or TLS versions. However, I'm unable to retrieve the body (since it's client beyond my control)
Therefore it would be nice to have API that could store the TLS report and this report could be retrievable by some kind of ID.
Something like
POST /create-link
( generated link in body response or header)Then I would be able to feed the client with a generated link.
After making a request on the generated link I would be able to retrieve the report - eg.
GET /generated-link/report
The text was updated successfully, but these errors were encountered: