zotero

History

Dan Stillman b5aeeaa60b 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 (cherry picked from commit `4bbae6e17a`)	2018-02-11 14:15:45 -05:00
..
zotero	Better handling of invalid HTTP responses	2018-02-11 14:15:45 -05:00
zotero-platform	2x grippy dimple	2017-12-01 13:09:06 -05:00

Dan Stillman b5aeeaa60b 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

(cherry picked from commit 4bbae6e17a)

2018-02-11 14:15:45 -05:00

zotero Better handling of invalid HTTP responses 2018-02-11 14:15:45 -05:00

zotero-platform 2x grippy dimple 2017-12-01 13:09:06 -05:00