Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

Print request and response json when debugging weaveproxy #1536

Merged
merged 2 commits into from
Oct 15, 2015
Merged

Conversation

bboreham
Copy link
Contributor

Fixes #1515

Simply added to debug-level logging, to avoid the added complexity of a new command-line flag to turn this on.

Thanks to @tomwilkie for the implementation

@tomwilkie
Copy link
Contributor

Worth noting not all commands use unmarshalRequestBody, so I don't think this covers everything.

@bboreham
Copy link
Contributor Author

ok you got me - which ones don't use it?

@rade
Copy link
Member

rade commented Oct 14, 2015

surely we want something in {un}marshalResponseBody too.

@rade
Copy link
Member

rade commented Oct 15, 2015

which ones don't use it

NullInterceptor, and and the no-op Intercept{Request/Response} of some other interceptors.

@bboreham
Copy link
Contributor Author

Ones we don't modify don't need to be printed.

@bboreham bboreham assigned rade and unassigned bboreham Oct 15, 2015
rade added a commit that referenced this pull request Oct 15, 2015
Print request and response json when debugging weaveproxy

Fixes #1515
@rade rade merged commit 5c114fc into master Oct 15, 2015
@rade rade added this to the 1.2.0 milestone Oct 15, 2015
@awh awh deleted the 1515-print-json branch November 9, 2015 16:40
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants