-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
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
pass profile parameters in JSON body #35
Conversation
please can you update the PR description so the motivation / benefit is clear to anyone outside of RAI, since this is an open-source package? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! :) 👏
Please do switch to JSON3 though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Update ProfileEndpoints version. Note that #35 introduced a breaking change in the sense we're no longer passing the profiling parameters for the `/debug_engine` endpoint in the query parameters, but are now passing them in the JSON body. Because of this I'm making this PR a major version bump.
This PR switches from passing the profiling parameters in the query parameters to passing them in the JSON body.
This makes it easier to forward requests to the /debug_engine endpoint from an intermediate service, which is now able to "blindly" forward the request to the /debug_engine endpoint without parsing and reconstructing the query parameters.