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
{{ message }}
This repository has been archived by the owner on Aug 20, 2024. It is now read-only.
I looked into the defaultProxyReqPathResolver and I am wondering why you use url.parse to parse the current requested url to extract the path. The koa documentation shows there is a ctx.request. path which already contains the path. Therefor we could save the expensive task of parsing a url. Or am I missing something that requires the url parsing here?
The text was updated successfully, but these errors were encountered:
I looked into the
defaultProxyReqPathResolver
and I am wondering why you useurl.parse
to parse the current requested url to extract the path. The koa documentation shows there is actx.request. path
which already contains the path. Therefor we could save the expensive task of parsing a url. Or am I missing something that requires the url parsing here?The text was updated successfully, but these errors were encountered: