Re: [w3c/ServiceWorker] NavigationPreloadManager.setHeaderValue should reject invalid HTTP header field values (#1000)

This can be fixed now and tested for. I wonder if perhaps you should be even more restrictive and limit the range to 0x20-0x7E or some such.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1000#issuecomment-432097831

Received on Tuesday, 23 October 2018 05:29:28 UTC