2056552 - [meta][graph] Protocol-specific handling of specific HTTP error response codes

Status: NEW

(MailNews Core :: Networking: Exchange, task)

Description

[Brendan Abolivier [:babolivier]]

In EWS, we can handle e.g. 400s, 404s, etc. as connectivity failures (i.e. the user has entered a URL that doesn't correspond to an EWS service) because all EWS requests share a single endpoint. However, with Graph, the actual API service might respond with 4XX if e.g. we're trying to create a folder with a name that conflicts with another folder, or we're trying to fetch a resource that cannot be found.

We already have some infrastructure for telling the OperationSender to use protocol-specific code with specific HTTP status codes (we use it to handle 429 errors), maybe we could extend that to e.g. all 4XX statuses. Though if we do this, we'll need some flexibility to detect e.g. 404s due to an invalid URL during a connectivity check.

Comment 1

[Brendan Abolivier [:babolivier]]

I'm turning this bug into a metabug that can be reused when we find more error codes that we want to handle in a protocol-specific way. The first case is bug 1892531 (i.e. propagating a 409 conflict with ErrorFolderExists as NS_MSG_FOLDER_EXISTS), but I suspect we'll find more as we go.