unfortunately I have no Windows machine at hand for testing, however running your workflow with your provided URL in KNIME 2.12.2 on OS X works fine for me.
Do other URLs work? Are you within a company network which requires specific proxy configuration?
yes I encountered the problem described on a company machine, using some proxy settings. But I performed my tests (as described) on the same machine - with both KNIME versions (even running them in parallel)!
Furthermore I reproduced my findings on another (company) PC, starting with 2.11.3 (everything fine) and than upgrading to 2.12.2 - with the result described!
Missing/wrong proxy configs was one of my first thoughts, but I have not found some new/additional/etc. settings for Paladin nodes in 2.12.2 - have I missed something?
Palladian's proxy configuration is picked from the Eclipse/KNIME configuration, and we haven't changed anything within Palladian recently (at least knowingly ;-) ). Have you checked, whether your settings in Preferences -> General -> Network Connections are identical on the working/non-working KNIME instance?
If that does not help, it would be very helpful if you could attach a DEBUG log output when running the workflow with the HttpRetriever (enable DEBUG level in Preferences -> KNIME -> KNIME GUI). It should give some output about the proxy config. used.