Empty header in default response causing parsing errors

[avocade]

As a somewhwat related issue to 29, we're getting an empty access-control-expose-headers: – with a CR immediately after the colon – on all our requests when using plug CORSPlug (regardless of setting origin: or not. This caused an internal http parsing lib written in C to bork out which took a while to debug… 💯

Non-null/emptystring return values for headers is not recommended if we want to make life easier for http parsers :)

Note: we're not using Phoenix, just a plain elixir app with plugs.

[mschae]

Hey @avocade is this still an issue? I believe we changed this behaviour to use null instead.

[mschae]

(Just released 1.4.0 because we introduced a new header that might be null (Vary) which is now fixed.)

[avocade]

On vacation, will be a while before I can verify this :) So I'll say it's closed for now.