Skip Ribbon Commands
Skip to main content
Version HistoryVersion History


Make a permanent 301 redirect instead of a 302

Assigned To

Johnsen, Bernie

Brief Description


Detailed Description

Is there any way to make a permanent 301 redirect instead of a 302? I’ve been conducting a lot of research lately and we’re really getting dinged on the temporary redirect. Google thinks and are two different sites and therefore we aren’t getting SEO credit when people link to the domain instead of the page.


Possible solution ideas: 



CRM AIS&D Ticket:






Johnsen, BernieNo presence information (11/22/2011 10:20 AM): Per email discussion with Scott I’ll push to sptest, and today.  I’ll then push to 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.
Demers, ScottNo presence information (11/21/2011 2:40 PM): The to redirect is assumed to be working correctly. I was not able to test because I'm not an admin on my machine.
Demers, ScottNo presence information (11/18/2011 2:47 PM): Was able to verify the 301 redirect with Fiddler. Test screen-shot attached. The second test to confirm to   failed. Error attached as well.
Johnsen, BernieNo presence information (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.
Fulbright, JeremyNo presence information (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?
Johnsen, BernieNo presence information (10/24/2011 1:37 PM): This is only currently configured on  See screen shot attached and comment from 10/14/11 4:36pm.
Demers, ScottNo presence information (10/24/2011 12:42 PM): UnlessI have the wrong server, Fiddler still shows this as a 302. See attachment.
Johnsen, BernieNo presence information (10/14/2011 4:40 PM): Assigning to Jeremy for testing.
Johnsen, BernieNo presence information (10/14/2011 4:38 PM): Correction to the entry below.  You must add two lines to your hosts file:
Delete those, save file and flushDNS when done.
Johnsen, BernieNo presence information (10/14/2011 4:36 PM): 301 has been configured on the dev farm at .  Please see fiddler to verify 301 vs 302 on home page redirection. 

Have also configure ate-sp-fe1 to demonstrate redirection of to  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 to 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 to be sure. 
Demers, ScottNo presence information (9/7/2011 12:01 PM): IIS setting could be the solution.
Fulbright, JeremyNo presence information (8/30/2011 3:30 PM): dependent on http modules. Requires extensive load testing.
Johnsen, BernieNo presence information (12/16/2010 11:12 AM): Assigned to Shilpa va CRM:
Correct 301 vs 302 Redirect issue

Example Page



(1) High

Priority Order



(3) In Progress

Start Date


Due Date


Release Date


Release Version


Server Deployment Status

(1) On Development: Building

Requested By

Fulbright, Jeremy

Ticket Status

1. Open

Workspace URL




Project Priority


Project Manager


Publicly Viewable?


Staging Date


Communication Type


Testing Procedure


SharePoint Environment


TFS Work Item



Content Type: Design or development task
Version: 29.0
Created at 11/22/2011 10:20 AM by Johnsen, Bernie