Re: [whatwg/fetch] Defining Access-Control-Expose-Headers parsing (#827)

I can't find the code in Chrome to handle Access-Control-Expose-Headers - it may use string composition, or some other mechanism.

Looking at the tests, I don't think any inconsistencies in Chrome are too likely to be related to https://crbug.com/896233 - that would only basically affect handling of the ",bb-8" and "Access-Control-Expose-Headers: bb-8,,@#$#%%&^&^*()()11!" tests, and I think the buggy old behavior would actually have made the first one more likely to have Chrome pass the test, and have no affect on whether the second one does.

@yutakahirano 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/827#issuecomment-435093988