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
We experienced significant issues with an older version of the axios package and our corporate proxy. Starting from a certain point in time, every second execution of some code would finish with an error. Before that, it occurred randomly:
When we enabled global-agent, all the problems disappeared. One of our colleague said that the problem lies in the infrastructure, not in axios itself.
Who is right? And why do you develop and maintain this "unnecessary" tool if the problem lies in the infrastructure? ;)
P.S. I'm not a Node.js expert. I'm responsible for the infrastructure, but I'm 100% sure that the packets were not reset (L4/TCP/RST), as suggested by the axios error below.
Best regards,
Maciek
The text was updated successfully, but these errors were encountered:
Hi,
We experienced significant issues with an older version of the axios package and our corporate proxy. Starting from a certain point in time, every second execution of some code would finish with an error. Before that, it occurred randomly:
When we enabled global-agent, all the problems disappeared. One of our colleague said that the problem lies in the infrastructure, not in axios itself.
Who is right? And why do you develop and maintain this "unnecessary" tool if the problem lies in the infrastructure? ;)
P.S. I'm not a Node.js expert. I'm responsible for the infrastructure, but I'm 100% sure that the packets were not reset (L4/TCP/RST), as suggested by the axios error below.
Best regards,
Maciek
The text was updated successfully, but these errors were encountered: