In some cases you may run into a case where it's not possible to continue within an interceptor and want to break out/cancel the request. This can be achieved by throwing an exception. This will not return a response and the request will not be executed.
Keep in mind that when throwing an exception you also need to handle/catch the exception in calling code.
For example if you want to stop the request if the token is expired:
class AuthInterceptor implements Interceptor {
@override
FutureOr<Response<BodyType>> intercept<BodyType>(Chain<BodyType> chain) async {
final request = applyHeader(chain.request, 'authorization',
SharedPrefs.localStorage.getString(tokenHeader),
override: false);
final response = await chain.proceed(request);
if (response?.statusCode == 401) {
// Refreshing fails
final bool isRefreshed = await _refreshToken();
if(!isRefreshed){
// Throw a exception to stop the request.
throw Exception('Token expired');
}
}
return response;
}
}
It's not strictly needed to throw an exception in order to break out of the interceptor. Other construction can also be used depending on how the project is structured. Another could be calling a service that is injected or providing a callback that handles the state of the app.
: Interceptor that prints curl commands for each execute request
: Interceptor that adds headers to each request
: Interceptor that logs request and response data
Both the CurlInterceptor and HttpLoggingInterceptor use the dart . In order to see logging in console the logging package also needs to be added to your project and configured.