Yeap, that is true :)

Thanks for the input.

The focus here was just to give an example on how to better handle cancelling an async request, and display some different error once this exception is caught so we could prove that it is how it work and you should catch the correct exception and treat it.

Maybe this exception handling is being handled somewhere else, like a global exception handler, and then the dev needs to throw it to not lose track of the context :D