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
It looks like with option of cors: true line 140 doesn't get hit, so line 168 sets the correct values. When using non-default CORS configuratoin, line 140 and line 160 get executed and the header values get duplicated.
I'm unclear as to a fix or what exactly are the conditions for both lines 140 and 168 to get executed. The first couple of tests in #2953 fail but don't double-append (nothing is appended). I added an assertion to 'matches allowed headers (Origin explicit)' test that executes both lines that shows the issue.
The three new tests you added are not necessary. The two that fail are because your config and origin do not match (missing tailing / in the config). The last change is the actual problem and I'll fix it shortly.
Access-Control-Expose-Headers
response headerHeader gets set in cors.js line 140 and get appended to in cors.js line 168
The text was updated successfully, but these errors were encountered: