-
Notifications
You must be signed in to change notification settings - Fork 123
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
doc for return response headers from v1 and v2 endpoints #417
Conversation
Signed-off-by: Andrews Arokiam <[email protected]>
✅ Deploy Preview for elastic-nobel-0aef7a ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@@ -65,6 +70,9 @@ if __name__ == "__main__": | |||
ModelServer().start([model]) | |||
``` | |||
|
|||
!!! note | |||
`return_response_headers=True` will be used to return response headers from v1 and v2 endpoints |
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.
`return_response_headers=True` will be used to return response headers from v1 and v2 endpoints | |
`return_response_headers=True` can be added to return response headers for v1 and v2 endpoints |
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.
This applies to preprocess, predict and postprocess also right?
self, | ||
payload: Dict, | ||
headers: Dict[str, str] = None, | ||
response_headers: Dict[str, str] = None, |
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.
Also add the example code you have to add the response header ?
Signed-off-by: Andrews Arokiam <[email protected]>
/lgtm |
"Fixes #issue-number" or "Add description of the problem this PR solves"
Proposed Changes