Plus meta refresh is awful for SEO. Though that might not be a problem for you.
On Monday, November 10, 2014, Russ Michaels <r...@michaels.me.uk> wrote: > > I would suggest doing so now then as it is a more efficient solution than > using meta refresh tags. > > > On Mon, Nov 10, 2014 at 21:22 PM, Steve LaBadie <slaba...@po-box.esu.edu > <javascript:;>> > wrote: > > > I didn't give it any thought. > > Steve LaBadie, Web Manager > East Stroudsburg University > 570-422-3999 > slaba...@esu.edu <javascript:;> <javascript:;> > > > > > -----Original Message----- > From: Russ Michaels [mailto:r...@michaels.me.uk <javascript:;> > <javascript:;>] > Sent: Monday, November 10, 2014 4:21 PM > To: cf-talk > Subject: Re: Redirects > > > Is there a specific reason you are not using url rewrite? > > > On Mon, Nov 10, 2014 at 21:17 PM, Steve LaBadie <slaba...@po-box.esu.edu > <javascript:;> > <javascript:;>> > wrote: > > > The Unix box (www) is going away and the www4 (windows box) will be renamed > www. I need to be able to recreate the directory without making a mess out > of the new server directory structure. I thought about creating a www > folder and putting all of the redirects/forwards in it. Is this possible? > > Steve LaBadie, Web Manager > East Stroudsburg University > 570-422-3999 > slaba...@esu.edu <javascript:;> <javascript:;> <javascript:;> > > > > > -----Original Message----- > From: Jon Clausen [mailto:jon_clau...@silowebworks.com <javascript:;> > <javascript:;> > <javascript:;>] > Sent: Monday, November 10, 2014 4:04 PM > To: cf-talk > Subject: Re: Redirects > > > Then use the Linux mod_rewrite redirect below on the current "www" box and > you should be good to go. Since you've got Linux on www, you could also > install NGINX (which makes a great HTTP proxy server) or use Apache to > proxy traffic to ww4 while maintaining the "www" in the URL. You'll need > to enable some IIS settings to allow for proxying and set a "www" handler > on that machine, but once you do, that's pretty much it. > > Apache Example with mod_proxy: > > <Location /> > ProxyPass http://www4.esu.edu > ProxyPassReverse http://www4.esu.edu > SetEnv force-proxy-request-1.0 1 > Order allow,deny > Allow from all > </Location> > > NGINX proxy example: > > server { > listen 80; > server_name esu.edu www.esu.edu; > access_log /var/log/nginx/esu.edu.access.log main; > > location / { > proxy_pass http://www4.esu.edu:80; > include /etc/nginx/proxy.conf; > } > } > > > Jon > > > On Nov 10, 2014, at 3:54 PM, Steve LaBadie <slaba...@po-box.esu.edu > <javascript:;> > <javascript:;> <javascript:;>> wrote: > > > > > www4 is a windows box > > > > Steve LaBadie, Web Manager > > East Stroudsburg University > > 570-422-3999 > > slaba...@esu.edu <javascript:;> <javascript:;> <javascript:;> > > > > > > > > > > -----Original Message----- > > From: Jon Clausen [mailto:jon_clau...@silowebworks.com <javascript:;> > <javascript:;> > <javascript:;>] > > Sent: Monday, November 10, 2014 3:54 PM > > To: cf-talk > > Subject: Re: Redirects > > > > > > Is the current "www4" a Linux or Windows machine? I would suggest > handling those at the web server level, with a 303 status code to let the > search engines know the redirect is temporary, rather than through the > application - with the exception of perhaps some dynamic redirects that > need to be changed "on-the-fly". Much more efficiently handled at the web > server level. > > > > Linux redirect to "ww4" example: > > > > RewriteCond %{HTTP_HOST} ^www\.esu\.edu [NC] RewriteRule ^(.*) > http://ww4.esu.edu$1 [L,R=307] > > > > > > Windows IIS web.config redirect example: > > > > <rule name="Redirect www2www4 temp" stopProcessing="true"> > > <match url="^(.*)$" ignoreCase="false" /> > > <conditions logicalGrouping="MatchAll"> > > <add input="{HTTP_HOST}" pattern="^(.*\.)www\.esu\.edu$" > ignoreCase="true" negate="true" /> > > </conditions> > > <action type="Redirect" url="http://ww4.esu.edu/{R:1}"; > redirectType="Temporary" /> </rule> > > > > HTH, > > Jon > > > > > > > > On Nov 10, 2014, at 3:39 PM, Steve LaBadie <slaba...@po-box.esu.edu > <javascript:;> > <javascript:;> > <javascript:;>> wrote: > > > >> > >> We are currently using a meta date redirect from a UNIX box. The > redirects currently sit on www and the production server sit at www4. We > are taking down www so the redirects have to be recreated on our new > production server which will be taking www. > >> > >> Current redirect structure: > >> <HTML> > >> <BODY> > >> <META HTTP-EQUIV=REFRESH > >> CONTENT="1;URL=http://www4.esu.edu/about/offices/police/index.cfm";> > >> </BODY> > >> </HTML> > >> > >> When the user types in www.esu.edu/police<http://www.esu.edu/police> > >> it > takes you to the correct page. We use this format to avoid long URLs on > marketing pieces. > >> > >> Can someone give me directions for best practices using CF. The new > production server currently runs CF9 but looking to upgrade to CF11. > >> > >> > >> Steve LaBadie, Web Manager > >> East Stroudsburg University > >> 570-422-3999 > >> slaba...@esu.edu <javascript:;> <javascript:;> <javascript:;><mailto: > slaba...@esu.edu <javascript:;> > <javascript:;> > >> <javascript:;>> > >> > >> [facebook-16x16]<http://www.facebook.com/eaststroudsburguniversity> > [twitter-16x16] <http://twitter.com/esuniversity> [youtube-16x16] < > http://www.youtube.com/user/esuedu> > >> > >> > >> > >> > > > > > > > > > > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:359606 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
