(11/22/2011 10:20 AM
): Per email discussion with Scott I’ll push to sptest, development.ucdenver.edu and staging.ucdenver.edu today. I’ll then push to www.ucdenver.edu
on Wednesday morning (11/30) at 4:00 am in advance of the changes which are UWS’s responsibility later that morning as part of the 6.9 push.
(11/3/2011 6:19 PM
): This can be implemented at any time as it doesn't require any restarts to any services or a .wsp deploy. This is just an IIS config change once we get the OK from UWS.
(10/31/2011 2:28 PM
): Scott, did confirm this is working as a 301 instead of 302 with Bernie? If so, can you let him know it's okay to release and include it with the other push items?
Delete those, save file and flushDNS when done.
(10/14/2011 4:36 PM
): 301 has been configured on the dev farm at http://spdev.ucdenver.edu
. Please see fiddler to verify 301 vs 302 on home page redirection.
Have also configure ate-sp-fe1 to demonstrate redirection of http://ucdenver.edu
. To test this you must configure your host file on your workstation. To do this, open C:\Windows\System32\drivers\etc\hosts with notepad and add the following entry to the bottom of that file :
Save and close the hosts file.
Close all browser windows
Open a command prompt (cmd.exe) and type: ipconfig /flushdns
Those three actions will force your local workstation to route to atel-sp-fe1 to test ucdenver.edu to www.ucdenver.edu
redirection. When done remove the last line from the host file and re-save. Repeat flushdns command.
I don't believe this will have any adverse affects on the production functionality, but, I'd highly recommend testing with the UWS scripts on spdev.ucdenver.edu to be sure.
Correct 301 vs 302 Redirect issue