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
If either plugin or endpoint sends an escape message/exception the post response plugins are not called anymore.
Depending on what you do in a post response plugin this may cause a memory leak. If a post plugin should release previously allocated memory and gets never called it could be a problem.
How about adding a boolean flag to the request or response struct if the request is still available for processing or has been aborted? And always execute the post response plugin. Then the post plugin could check if it actually needs to do something.
And the post response plugins are also not called if an previous plugin return *off.
If either plugin or endpoint sends an escape message/exception the post response plugins are not called anymore.
Depending on what you do in a post response plugin this may cause a memory leak. If a post plugin should release previously allocated memory and gets never called it could be a problem.
How about adding a boolean flag to the request or response struct if the request is still available for processing or has been aborted? And always execute the post response plugin. Then the post plugin could check if it actually needs to do something.
And the post response plugins are also not called if an previous plugin return *off.
The text was updated successfully, but these errors were encountered: