If your extension is hosted in the Google Chrome extension gallery, ignore this page. You don't need to worry about HTTP headers because the gallery handles them for you.

If you intend to use another server, make sure it serves appropriate HTTP headers, so that users can install your extension by clicking a link to it.

Google Chrome considers a file to be an extension if either of the following is true:

• The file has the content type application/x-chrome-extension
• The file suffix is .crx and both of the following are true:
  • The file is not served with the HTTP header X-Content-Type-Options: nosniff
  • The file is served with one of the following content types:
    • empty string
    • "text/plain"
    • "application/octet-stream"
    • "unknown/unknown"
    • "application/unknown"
    • "*/*"

The most common reason for failing to recognize an extension is that the server sends the header X-Content-Type-Options: no sniff. The second most common reason is that the server sends an unknown content type — one that isn't in the previous list. To fix an HTTP header issue, either change the configuration of the server or try hosting the extension at another server.