Case insensitive Content-Type not handled as html

[fliespl]

If mailer uses content-type, Content-type instead of Content-Type message will not be displayed as html since case sensitive key match is being used in controller.js.

[ian-kent]

I think this is the same as mailhog/MailHog#113, and should be fixed by c2d0e00

Let me know if it's still broken after the next release

[123andy]

Hi @ian-kent - The case sensitivity of the header keys is still an issue. It appears the code uses Content-Type explicitly in numerous places:

Perhaps instead of the patch above, a fix that modifies the message.Content.Headers['keys'] to be of the proper format on parse would be easier:

for(var header in message.Content.Headers) {
	if(header.toLowerCase() == 'content-type' && header != 'Content-Type') {
		message.Content.Headers['Content-Type'] = message.Content.Headers[header];
		delete message.Content.Headers[header];
		break;
	}
}

Or, perhaps just make all titlecase:

for(var header in message.Content.Headers) {
  var parts = header.split("-");
  for (var part in parts) {
    var s = parts[part];
    parts[part] = s.charAt(0).toUpperCase() + s.substr(1).toLowerCase();
  }
  var newHeader = parts.join("-");
  if(header =! newHeader) {
    message.Content.Headers[newHeader] = message.Content.Headers[header];
    delete message.Content.Headers[header];
  }
}

[webprogrammierer]

The problem still exist. Why can't this be solved?

[dimitropoulos]

@ian-kent since you asked, just wanted to let you know that it's still an issue

[webprogrammierer]

For years