jasimon9 - 11:45 pm on Feb 6, 2013 (gmt 0)
I appreciate your response, and it does not drive me bonkers. I reserve getting bonkers-driven for things other than people trying to help me.
Just an update. I have not had a chance to examine the details necessary to answer questions of lucy24. But I have made some progress in general and am reporting on that.
I am trying to get away from the Windows environment because it is too much out of sync with our main development and production environments. So debugging that becomes academic.
Part of the problem I have been having is that on our production, test, quality and "regular" development environment we have name-based vhosts. Plus SSL. But on the environments on my own workstations, for reasons not worth going into, I had port-based vhosts. This seems to cause problems with SSL when redirecting, as it becomes very confusing as to whether the connection should be SSL or not as the port-based SSL takes over from the port-based vhost.
This may or may not be a problem, but I am changing from port-based to name -based everywhere.
What happens to cause the confusion, is that after being redirected to the pretty url, which is in SSL, later site accesses lose the port. But that is not valid, so the url in the address bar has to be manually modified to have the port. It goes like this in the address bar:
[localhost:8080...] --> click
https://localhost/prettyurl (note that the 8080 has disappeared probably due to the port-based SSL --> click
[localhost...] giving page not found error, until 8080 is manually put back into the url
Yet as stated, by going to entirely name-based vhosts, I am hoping to eliminate this issue. I have not gotten that far yet.