Open Mahdhir opened 3 weeks ago
@Mahdhir you should use no-cache
from your fetch
.
Ref: https://github.com/ProxymanApp/Proxyman/issues/2038#issuecomment-2143324535
@Mahdhir you should use
no-cache
from yourfetch
. Ref: https://github.com/ProxymanApp/Proxyman/issues/2038#issuecomment-2143324535
@NghiaTranUIT 'no-cache' is already included. This works fine on normal server components. Only middlewares seem to cause an issue, probably because they have their own edge runtime.
yeah, it can be the case. NextJS might use their own logic to handle the middleware, so it might not use the Proxy setting.
Description
Proxyman is not capturing traffic on the edge runtime. But normal requests under the route handlers, and server components show up on proxyman.
Steps to Reproduce
Current Behavior
Proxyman is not capturing traffic on the edge runtime next js middleware.
Expected Behavior
Proxyman should capture all traffic including next js middleware edge runtime.
Environment
Proxyman Version 5.7.0 (50700) | macOS: Version 14.6.1 (Build 23G93)