Skip to content
This repository has been archived by the owner on May 18, 2021. It is now read-only.

HTTP trace mode #129

Closed
nickatsegment opened this issue Mar 6, 2019 · 2 comments
Closed

HTTP trace mode #129

nickatsegment opened this issue Mar 6, 2019 · 2 comments

Comments

@nickatsegment
Copy link
Contributor

nickatsegment commented Mar 6, 2019

It would be nice for debugging if we could dump all HTTP traffic.

  • Some of our errors are not detailed enough to debug, and without making a big error hierarchy, HTTP dumps are probably easier to deal with
  • We use some undocumented janky Duo APIs that would be easier to dev against if we could just do a packet/SSL capture
  1. patch the HTTP clients with a TLS key logger (follow https://golang.org/pkg/crypto/tls/#example_Config_keyLogWriter)
  2. do a packet capture

Related:

@stale
Copy link

stale bot commented May 5, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label May 5, 2019
@nickatsegment
Copy link
Contributor Author

Meh, this wiki article is probably good enough https://github.com/segmentio/aws-okta/wiki/HTTP-debugging

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant