- From: youennf <notifications@github.com>
- Date: Tue, 07 Feb 2017 07:47:28 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 7 February 2017 15:49:03 UTC
Yes, the process is lossy. We might end up loosing some header casing information as well for well known header names. WebKit internal structure is a map which is lossy. It seems good that the header API is sanitising things and makes things consistent amongst browsers. As of Request/Response constructors, we could special case the transfer of headers in a "lossless" way. We could also put the burden on web developers to be extra careful at how they use the API in those edge scenarios. -- 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/481#issuecomment-278040151
Received on Tuesday, 7 February 2017 15:49:03 UTC