It seems Safari enters into this mad behaviour when you have accessed localhost using a client side certificate. In my case, one of the projects I work with needs this client side setup and it totally ...