Dan Stillman 4bbae6e17a Better handling of invalid HTTP responses ... If a server returns an invalid HTTP response (e.g., Content-Encoding: gzip with a plaintext body, a.k.a. NS_ERROR_INVALID_CONTENT_ENCODING) but we can still parse a 4xx or 5xx HTTP response code, use that for the XHR status, since it might be enough for what we need to do (e.g., verify a 404 from a WebDAV server). This fixes a current problem with Box [1]. Also fix a "msg is not defined" error when the XHR status is 0 but the SSL connection is fine and include the channel and response status on the UnexpectedStatusException object (though both of these would now only happen on an invalid 2xx response, when the XHR status would remain as 0). [1] https://forums.zotero.org/discussion/comment/301014/#Comment_301014		2018-02-10 22:18:45 -05:00
..
content	Better handling of invalid HTTP responses	2018-02-10 22:18:45 -05:00
locale	Update locales from Transifex and merge new English strings	2018-02-08 03:23:16 -05:00
skin/default/zotero	Reduce minimum width of Zotero pane to 670px	2018-01-30 19:12:05 -05:00