Changed proxyConfig.context
to return a bool when headers.accept
is undeclared.
#8966
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi 👋,
I had some issues with using the default proxy heuristics with my own websocket server. So I did some digging and as far as I can tell the
proxyConfig.context
function returnsundefined
if theaccept
header is missing.So I added a quick test
prepareProxy.test.js
that usesproxyConfig.context
to filter a few mocked requests to check if they get proxied (returns true to proxy, false otherwise). And sure enough when testing path name/socket/proxy
without anaccept
header it results inundefined
. I expect it to be true since since it should be proxied according to the default heuristics described in your documentation / comments.So I changed
proxyConfig.context
to ensure that both themethod: GET
andAccept: text/html
check always returns a bool, and if they'refalse
only then callingmayProxy()
for a final check!Passes the new tests and closes #5280