Skip to content

allow specifying which QBXML errors should be fatal#202

Open
Elemecca wants to merge 1 commit into
consolibyte:masterfrom
Elemecca:t-error-threshold
Open

allow specifying which QBXML errors should be fatal#202
Elemecca wants to merge 1 commit into
consolibyte:masterfrom
Elemecca:t-error-threshold

Conversation

@Elemecca
Copy link
Copy Markdown

Currently any nonzero status code received in the XML sent to receiveResponseXML is considered a fatal error and the QBWC session is torn down. That's incorrect according to the QBXML documentation, which says that codes 1-499 are informational and 500-999 are warnings. This adds a new configuration key, status_error_threshold, which is the minimum status code which should be considered a fatal error. To preserve reverse compatibility the default is set to 1.

Currently any nonzero status code received in the XML sent to
`receiveResponseXML` is considered a fatal error and the QBWC
session is torn down. That's incorrect according to the QBXML
documentation, which says that codes 1-499 are informational
and 500-999 are warnings. This adds a new configuration key,
`status_error_threshold`, which is the minimum status code
which should be considered a fatal error. To preserve reverse
compatibility the default is set to 1.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant