When I was writing Rating 26 years of Java changes, I started reflecting on the new HttpClient library in Java 11. The old way of fetching a URL was to use URL.openConnection(). This was intended to be a generic mechanism for retrieving the contents of any URL: files, web resources, FTP servers, etc. It was a…

NeilMadden's blog is a resource for developers and software engineers seeking to enhance the security and efficiency of their programs. Covering topics such as secure coding practices, encryption techniques, and vulnerability management strategies, it offers practical insights and actionable advice to mitigate security risks effectively. Through detailed tutorials, code examples, and expert commentary, the blog equips its audience with the knowledge and tools needed to build robust and resilient software solutions in today's digital landscape.

Neil Madden

Explores the evolution of URL handling in Java, questioning whether generic URL APIs like URL.openConnection() were a good design choice. The author argues that Java 11's HttpClient, being protocol-specific rather than generic, represents better API design. Generic URL handling introduces security risks, performance unpredictability, and forces lowest-common-denominator APIs. Modern applications typically handle a single URL scheme and benefit from specialized, focused implementations rather than attempting universal URL support.

Were URLs a bad idea?

<p>URL’s are a good idea thou, i like it simply because its simple and easy to understand.</p>
