You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clients using AlamoFire should be able to submit NEL reports using the Report-To header in HTTP. This means understanding network failures on the device such as TCP timeouts, resets, aborts, TLS certificate failures, DNS failures, and protocol failures.
What happened instead?
Mobile clients that want to use Network Error Logging cannot upload network error reports to targeted endpoints.
Alamofire Environment
Alamofire version: all Xcode version: all Swift version: all Platform(s) running Alamofire: all macOS version running Xcode: all
Demo Project
As this is a new feature, any project will reproduce the issue.
The text was updated successfully, but these errors were encountered:
While it's unlikely we'd actually support the NEL standard (it's complex and seems to be of rather limited utility), an analysis of what would be need for support outside Alamofire itself would be a good idea to guide future development.
jshier
changed the title
[FeatureRequest] NEL support in Alamofire
Network Error Logging Support in Alamofire
Nov 10, 2020
What did you do?
NEL (network error logging) is not supported in AlamoFire.
What did you expect to happen?
Clients using AlamoFire should be able to submit NEL reports using the Report-To header in HTTP. This means understanding network failures on the device such as TCP timeouts, resets, aborts, TLS certificate failures, DNS failures, and protocol failures.
What happened instead?
Mobile clients that want to use Network Error Logging cannot upload network error reports to targeted endpoints.
Alamofire Environment
Alamofire version: all
Xcode version: all
Swift version: all
Platform(s) running Alamofire: all
macOS version running Xcode: all
Demo Project
As this is a new feature, any project will reproduce the issue.
The text was updated successfully, but these errors were encountered: