| OLD | NEW |
| 1 <div id="pageData-title" class="pageData">Hosting</div> | 1 <div id="pageData-name" class="pageData">Hosting</div> |
| 2 | 2 |
| 3 <p> | 3 <p> |
| 4 If your extension is hosted in Google's | 4 If your extension is hosted in Google's |
| 5 <a href="https://chrome.google.com/extensions">gallery</a>, | 5 <a href="https://chrome.google.com/extensions">gallery</a>, |
| 6 <em>ignore this page</em>. | 6 <em>ignore this page</em>. |
| 7 You don't need to worry about HTTP headers | 7 You don't need to worry about HTTP headers |
| 8 because the gallery handles them for you. | 8 because the gallery handles them for you. |
| 9 </p> | 9 </p> |
| 10 | 10 |
| 11 <p> | 11 <p> |
| (...skipping 41 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 53 The most common reason for failing to recognize an extension | 53 The most common reason for failing to recognize an extension |
| 54 is that the server sends the header | 54 is that the server sends the header |
| 55 <code>X-Content-Type-Options: no sniff</code>. | 55 <code>X-Content-Type-Options: no sniff</code>. |
| 56 The second most common reason | 56 The second most common reason |
| 57 is that the server sends an unknown content type — | 57 is that the server sends an unknown content type — |
| 58 one that isn't in the previous list. | 58 one that isn't in the previous list. |
| 59 To fix an HTTP header issue, | 59 To fix an HTTP header issue, |
| 60 either change the configuration of the server | 60 either change the configuration of the server |
| 61 or try hosting the extension at another server. | 61 or try hosting the extension at another server. |
| 62 </p> | 62 </p> |
| OLD | NEW |