Perhaps. I've never seen anything like this reported with my patches, but as you well know, redirects and IE 5 have had problems that get expressed in my patches, so I am not saying it couldn't be.
Do you see this when you include the port number (and so bypass nsvhr?) Do you see this when you use nsvhr/nssock (and not nsvhr/nsunix?)
