The UX when a network error occurs, should be improved. Currently: 1. Create a new library 2. Select "Springer" in "Web search" 3. Search for "test" 4. Result:  Expanding the error results in  ## Tasks - [ ] Expected output: HTTP error 403 occurred when fetching from {URL}. - [ ] The secrets should be removed from the URL. (Currently, the key is shown. See screenshot; the blurred part) --- Other place, where it works as expected (!) 1. I create an entry 2. Navigate to "General" 3. In the "File" field, "Download from URL"  7. I paste <https://www.researchgate.net/profile/Joanna-Kosinska-3/publication/344415012_Autonomic_Management_Framework_for_Cloud-Native_Applications/links/5f73246a458515b7cf567d65/Autonomic-Management-Framework-for-Cloud-Native-Applications.pdf> 8. Output  - [ ] If possible, also add the API key removal, here, too. The log file of JabRef shows the full exception:  --- - Another example <https://www.researchgate.net/profile/Giuseppe-Muntoni-2/publication/344494377_Mining_the_Architecture_of_Microservice-Based_Applications_from_their_Kubernetes_Deployment/links/5f7c7b0b458515b7cf6a51bd/Mining-the-Architecture-of-Microservice-Based-Applications-from-their-Kubernetes-Deployment.pdf?origin=publication_detail> - Discourse discussion: https://discourse.jabref.org/t/a-network-error-when-i-use-the-jabref-to-manage-my-references/4274
The UX when a network error occurs, should be improved.
Currently:
Expanding the error results in
Tasks
Expected output:
The secrets should be removed from the URL. (Currently, the key is shown. See screenshot; the blurred part)
Other place, where it works as expected (!)
The log file of JabRef shows the full exception: