René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"API works only partially when using an HTTP proxy","articleBody":"TL;DR:  Please add support for HTTP proxies in all API parts using Apache HttpClient\n\nLong version:\n\nI tried to use the nextcloud-java-api within a company network which requires me to use an HTTP proxy to access the Nextcloud instance.\n\nThis is my sample code demonstrating that parts of the API work with an HTTP proxy an some do not work (the ones using Apache HttpClient):\n\n\tSystem.setProperty(\"http.proxyHost\", \"proxy\");\n\tSystem.setProperty(\"http.proxyPort\", \"8000\");\n\tSystem.setProperty(\"https.proxyHost\", \"proxy\");\n\tSystem.setProperty(\"https.proxyPort\", \"8000\");\n\n\tNextcloudConnectorconnector = new org.aarboard.nextcloud.api.NextcloudConnector(\"my_cloud_host\", true, 443, user, password);\n\tSystem.out.println(\"connector.getServerVersion() = \" + connector.getServerVersion());  \u003c-- works fine because it does not use Apache HttpClient\n\n\tUser user = connector.getUser(\"my_user_name\");  \u003c-- fails with a timeout because Apache HttpClient doesn't automatically use the HTTP proxy settings of Java\n\nThe problem is that in ConnectorCommon.java the HttpClient is hard coded via\n\n\tHTTPC_CLIENT = HttpAsyncClients.createDefault();\n\nSo this could be either replaced by a function which can be overwritten so that the user himself can set up an HttpClient with the appropriate proxy configuration or the API could read the Java http proxy settings and set the corresponding properties of the HttpClient.","author":{"url":"https://github.com/xylo","@type":"Person","name":"xylo"},"datePublished":"2025-10-21T14:46:07.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/92/nextcloud-java-api/issues/92"}