The default CookieHandler as returned by CookieHandler.getDefault() is null.
That is OK, if this behaviour is specified by javadoc specification.
Currently, getDefault says nothing about the return value and its meaning of
CookieHandler.getDefault() method. setDefault(CookieHandler) method
specification also says nothing on what should be the behaviour in response to
null (should it unset the current cookie handler or throw an exception?).
Either the reference implementation should provide a default cookie handler or
completely specify the behaviour. Current specification is not enough to allow
implementors compatible cookie handlers since it leaves many aspects of
CookieHandler behaviour blank.