News for hackers. Stuff that matters.
Re:Common I/O Tasks in Modern Java by yen223 on Friday August 02, 2024 @07:27PM (#41143520)
When you do equality checks on two URL instances, it checks to see if they resolve to the same IP address by hitting up DNS. This is problematic because equality checks happen implicitly all the time, e.g. if you're putting URLs into a hashtable.

https://docs.oracle.com/javase/8/docs/api/java/net/URL.html#...

Re:Common I/O Tasks in Modern Java by TheNightman on Friday August 02, 2024 @08:12PM (#41143739)
No shot this is _ever_ what is actually meant by ‘if urlA == urlB’
Re:Common I/O Tasks in Modern Java by hn_throwaway_99 on Friday August 02, 2024 @08:25PM (#41143808)
Well, remember, this is Java, so `if (urlA == urlB)` just does standard object equality, the IP lookup is only done for `if (urlA.equals(urlB))` :)
Re:Common I/O Tasks in Modern Java by metadat on Friday August 02, 2024 @11:08PM (#41144407)
It's still insane behavior. This implementation is effectively a sharp edge in the dark. Have fun.. :-/
Re:Common I/O Tasks in Modern Java by yen223 on Tuesday August 06, 2024 @07:50PM (#41176768)
This is Java, so you should always do `Object.equals(urlA, urlB)`, on the off-chance urlA is null!

(I do not miss working in Java haha)

Re:Common I/O Tasks in Modern Java by layer8 on Friday August 02, 2024 @09:15PM (#41143989)
Yes. Use the newer URI class instead if you want a value object without “smarts”. URL instances also contain a URLStreamHandler, which means that two URL instances that compare equal can still have different URLStreamHandlers that handle the URL differently. Instances of the class URL are really service objects.