This is more of a this is technically correct change than a necessary, functional one. We definitely are serializing to JSON, so the blob contents are technically an "application/json" type (see http://www.ietf.org/rfc/rfc4627.txt). I'm proposing this change primarily to help third-party tools automatically identify the content-type properly, and just because it's the right thing to do. I can't think of anything that this code change would break for any existing code or stored data.
With that said, if anyone can think of a reason not to take this change, I'm open to hearing why.
This is more of a this is technically correct change than a necessary, functional one. We definitely are serializing to JSON, so the blob contents are technically an "application/json" type (see http://www.ietf.org/rfc/rfc4627.txt). I'm proposing this change primarily to help third-party tools automatically identify the content-type properly, and just because it's the right thing to do. I can't think of anything that this code change would break for any existing code or stored data.
With that said, if anyone can think of a reason not to take this change, I'm open to hearing why.
Thanks! Scott