http exception should come with text

[koppor]

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"
4. 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
5. 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

[RehanChalana]

I'd like to work on this issue, but I don't have a detailed plan yet. Could someone provide some guidance on the best way to approach this?

Thanks!

[github-actions[bot]]

Welcome to the vibrant world of open-source development with JabRef!

Newcomers, we're excited to have you on board. Start by exploring our Contributing guidelines, and don't forget to check out our workspace setup guidelines to get started smoothly.

Having any questions or issues? Feel free to ask here on GitHub. Need help setting up your local workspace? Join the conversation on JabRef's Gitter chat. And don't hesitate to open a (draft) pull request early on to show the direction it is heading towards. This way, you will receive valuable feedback.

Happy coding! 🚀

[koppor]

@RehanChalana I am not sure how I can help you. Could you reproduce the output? If yes, then search in the code where the output is generated, how it flows through the code. And where the HTTP error message is shown. If not, please explain at which step you could not follow.

[RehanChalana]

Yes i was able to reproduce the output and yes i am following the stack trace to understand the flow and the source of HTTP error.

Thanks for assistance