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
I develop a plugin to sign for response from upstream services.
This sign plugin has been working properly for a long time. But today i observed that i enable ext-plugin-post-resp plugin the request can't reach the upstream service. The response from APISIX is as follows
<html><head><title>502 Bad Gateway</title></head><body><center><h1>502 Bad Gateway</h1></center><hr><center>openresty</center><p><em>Powered by <ahref="https://apisix.apache.org/">APISIX</a>.</em></p></body></html>
There is no log in my upstream service.
Apisx access log is as follows
Description
I develop a plugin to sign for response from upstream services.
This sign plugin has been working properly for a long time. But today i observed that i enable
ext-plugin-post-resp
plugin the request can't reach the upstream service. The response from APISIX is as followsThere is no log in my upstream service.
Apisx access log is as follows
The response is normal when i curl in my APISIX pod. So i think the network is normal. Like that
Many routes are using this plugin, but only a few are experiencing this.
The route is as follow
When i disable
ext-plugin-post-resp
the route return to normal.Access log:
Response:
Generally speaking ,
ext-plugin-post-resp
will be called after response. I wonder why the upstream can't accept request.Environment
3.8.0
0.4.0
The text was updated successfully, but these errors were encountered: