Yongwoo Jung

Hi @FDiskas 😀 Thanks for reporting the problem. I tried to reproduce it in my local environment, but it doesn't work. When using this middleware, did the memory gradually increase,...

@FDiskas Thank you for the explanation. 😀 Could you tell me what version of next-http-proxy-middleware you are currently using for your project? Prior to v1.0.10, memory leaks may have occurred...

It is not yet accurate, but it seems that system memory accumulates in the inspector when repeatedly requested several times using the ab test.. I'll check a little more. 🤔...

> As I noticed that there is a new release I updated as soon as possible but didn't noticed any improvement regarding memory 😭

If possible, try applying the code like this: (The problem I've identified is that when a promise(async) is exported, the memory increases with the increase in requests.) ```ts // as-is...

Hi @FDiskas, Please do not return promise(await function) 😭 Is there any reason to use the async~await? ```ts export default async (req: NextApiRequest, res: NextApiResponse) => { //

> Tested - still memory is increasing - I used code like so > > ```tsx > export const config = { > api: { > bodyParser: false, > externalResolver:...

> Thank you for good explanation. > In this case no errors in requests was thrown. But as you said probably I need to ignore such small memory changes. >...

Hi @ctrlaltdylan Thanks for your reporting 😀 I have a few questions to check this issue. * Can you tell me the URL value to input from the client and...

Hi @wansiedler It seems to be possible to use multiple targets by implementing it like the code below. ```ts export default (req: NextApiRequest, res: NextApiResponse) => { const proxyOptions =...