Cmon, this is as backward as the "do not track" header... asking websites to explicitly opt out... in order to protect users from the users's own browser!?
So, I was experimenting with this concept yesterday but couldn't get it to work...
How do you set up a local proxy to do this kind of stuff? I got up to the point of changing request/response headers but couldn't manage to actually edit the data going through, esp when dealing with ssl (which is the point really, of ssl).
Let's say, Chrome has a bug that causes a crash unless you send Workaround-Chrome-Bug header. Why wouldn't you send the header until the bug is fixed in Chrome?
Because the intent is the complete opposite, to add, not remove the bug... what else are they going to add, how many more headers are we going to end up with, what if the other browsers join in... this is not sustainable, but it's not supposed to be - they are betting on the fact that 99% of website owners will not even be aware of this issue let alone know how to configure their web server or be bothered to - it's purely for the purpose of saying "we allow you to opt out".
Saying "oh but we can thwart them with a header" is just naive, Google would like you to believe that. Look at the bigger picture.
No, just don't build stupid things into browsers.