MvdV>> When I connect form an IPv4 only client, no problem.
MvdV>> When I try to connect from an IPv6 capable client: Error 404.
MvdV>> Can anyone confirm? Or explain?
WV> When I connect from this virtual XP which is IPv4 only, I also get the WV> 404 error.
Very odd. When I connect from Rosa's machine (WinXP) I get the site as expected. When I connect (My laoptop Win10) I get the 404. My laptop and Rosa's machine are presently not IPv6 connected.) From my Fido machine (WinXp, IPv6 connected via SixXs) I get the error 404. When I set network.dns.disableIPv6 in aout:config to true, I do not get the 404, but see the site as expected.
WV> And as the 404 error is generated by the server.
I noticed that too.
WV> I think you still have the page in your browser cache on the IPv4 WV> client.
Nope. It could not have been in the cache, as it was the first time I saw the actual apage unstead of the custom 404 page.
WV> Can you try a refresh, and see what happens?
Nothing unexpected.
There is something fishy going on and it does seem to be loosely IPv6 related. But I can't put the finger on it...
Later..
It gets even weirder. The error is on only that subpage. The main page of that site, vandekraats.net displays as expected on all machines here.