From f0f400cb2e0a3c545d723524e8bbaf136caacf81 Mon Sep 17 00:00:00 2001 From: "kathyw@google.com" Date: Sat, 3 Oct 2009 03:55:14 +0000 Subject: A new page about hosting extensions (i.e. serving the right HTTP headers). TBR=aa Review URL: http://codereview.chromium.org/243085 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@27936 0039d316-1c4b-4281-b951-d872f2087c98 --- chrome/common/extensions/docs/hosting.html | 439 +++++++++++++++++++++++++++++ 1 file changed, 439 insertions(+) create mode 100644 chrome/common/extensions/docs/hosting.html (limited to 'chrome/common/extensions/docs/hosting.html') diff --git a/chrome/common/extensions/docs/hosting.html b/chrome/common/extensions/docs/hosting.html new file mode 100644 index 0000000..2224c02 --- /dev/null +++ b/chrome/common/extensions/docs/hosting.html @@ -0,0 +1,439 @@ + + + + + + + Hosting
+ + +
+ + +
+
+ paramName + + + +
+ ( + optional + + + Type + + + + array of + + paramType + + + ) +
+ + +
+
+ Undocumented. +
+
+ Description of this parameter from the json schema. +
+ + +
+
+
+
+
+
+
+
+
+ +
+ + + + + +
+ + + +
+ + + + + +
Hosting
+ +

+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. +

+
+ + + +
+
+ +
+ + -- cgit v1.1