4 ms·

I have two questions: 1. Do I understand it correctly and the validation header is individual for each installation? 2. Is this header only in Google Chrome o

• gruez 1y ago
  >1. Do I understand it correctly and the validation header is individual for each installation? I'm not sure how you got that impression. It's generated from fixed constants. https://github.com/dsekz/chrome-x-browser-validation-header?tab=readme-ov-file#how-the-header-is-made https://github.com/dsekz/chrome-x-browser-validation-header?...
  • exiguus 1y ago
    It's still not clear to me because it's called the default API key. And for me, default means that this is normally overwritten. And if overwritten, during build or during install? That's what I'm asking myself.
• dlenski 1y ago
  I had the same question (2). https://news.ycombinator.com/item?id=44560664 https://news.ycombinator.com/item?id=44560664 If it's only in the closed-source Chrome, then it seems it's intended to help Google's servers distinguish between Google's own products and others. But I've never seen a Google site which worked less-well in Chromium than in Chrome, so I'm somewhat skeptical of this. Perhaps there are exceptions