302 redirect on http but not on https

Direct_Ram

Hi

I have noticed using screaming frog that 302 redirect is in place but when checking the HTTACESS there no such thing in place.

If I run a scan with: http://www.redirect-checker.org/index.php doing a test with: https://www. everything seems ok but then when I do: http://www. There is a 302 in place and seem to understand why.

I have analysed the Httacess file and cant seem to locate anything that refers to the 302 any advise or previous experience would be great.

Thanks
E

BlueprintMarketing

you're running Apache tomcat right?

301 Redirect URLs.

Redirect 301 /holidays/about-direct-traveller/british-travel-awards.asp /directtraveller/awards
Redirect 301 /directtraveller/holidays/about-direct-traveller/british-travel-awards.asp /directtraveller/awards

I am guessing this simply from you having this port open and having no issues with HTaccess 8443 is the default port of tomcat with ssl

http://beamusup.com/generate-htaccess/

BlueprintMarketing

Johnson I agree thumbs up with Nginx could definitely be a as reverse proxy. the best way to tell would be to scan the ports but I will allow him to do that.

I agree with you as well on the 302 issue

He has to redirect using a 301 instead of a 302 from

https://www.directtraveller.com/holidays/about-direct-traveller/british-travel-awards.asp

https://www.directtraveller.com/awards
I bet there are a few other 302's in there if there are one however I'm speculating. Crawling the site withhttps://www.deepcrawl.com/ or http://www.screamingfrog.co.uk/seo-spider/ will show him any 302's as far as the best way to redirect I agree with you again it is based on what type of server he is using.

If MS ASP

Ues

http://www.rapidtables.com/web/tools/redirect-generator.htm

http://www.rapidtables.com/web/dev/url-redirect.htm#asp-redirect

ASP redirect

old-page.asp:

<%@ Language="VBScript" %>
<%
' ASP permanent URL redirection
Response.Status="301 Moved Permanently"
Response.AddHeader "Location", "http://www.mydomain.com/new-page.html"
Response.End
%>

http://ask.webatall.com/nginx/17733_nginx-redirect-http-to-https-and-non-www-to-ww.html

From feed the bot you can see your site is unfortunately using 302's maybe that's on purpose if not you should change it to 301's.

Final status code: 200
1 Redirect(s)
https://www.directtraveller.com/holidays/about-direct-traveller/british-travel-awards.asp
** 302 redirect**
https://www.directtraveller.com/awards

If is is a Proxy

http://wiki.nginx.org/HttpProxyModule#proxy_redirect

http://wiki.nginx.org/Pitfalls#Using_If

PS

I would remove the nofollow on these links. Google likes TOS and privacy policies

Nofollow links

3 nofollow links

/terms-and-conditions
/resources
/privacy-policy checked using http://www.feedthebot.com/tools/

all the best,

Tom

Direct_Ram

We have a redirect from HTTP to HTTPS and then have the following redirect on the httaccess file:

#Redirect /directtraveller/holidays/about-direct-traveller/british-travel-awards.asp /directtraveller/awards

Redirect /holidays/about-direct-traveller/british-travel-awards.asp /directtraveller/awards

TheWebMastercom

Not necessarily. He could be using Nginx as reverse proxy.

He already said the http to https is working fine with my suggestion. The problem is the redirect from one URL to another which what I gave him for the .htaccess doesn't address at all.

ie.

https://www.directtraveller.com/holidays/about-direct-traveller/british-travel-awards.asp
to
https://www.directtraveller.com/awards

BlueprintMarketing

The reason why the HTaccess file is not working for you is because you're running a server on Nginx instead of Apache's .htaccess your server uses a "nginx config" this is why .htaccess will not work properly. this will also show you why you're still running a 302 redirect instead of a 301 redirect

http://www.redant.com.au/ruby-on-rails-devops/manage-ssl-redirection-in-nginx-using-maps-and-save-the-universe/

https://www.digitalocean.com/community/questions/http-https-redirect-positive-ssl-on-nginx

for referencing these URLs below will tell you everything you need to know about your configuration and how to set it up. I've placed a lot of redirects below because there are so many different ways of doing this below the two URLs where it says I recommend using this is the configuration that should be default on your server in order to force SSL

http://nginx.org/en/docs/http/ngx_http_rewrite_module.html#return

http://nginx.org/en/docs/http/ngx_http_core_module.html#server_name

** I recommend using this to fix use this on your nginx config file**

_**`server {
       listen         80;
       server_name    www.domain.com;
       return         301 https://$server_name$request_uri;
}

server {
       listen         443 ssl;
       server_name    www.domain.com;

       [....]
}`**_

might be easier this way

<code>server {
       listen         80;
       server_name    my.domain.com;
       return         301 https://$server_name$request_uri;
}

server {
       listen         443 ssl;
       server_name    my.domain.com;

       [....]
}</code>

you are still putting out 302's I double checked your server

http://www.feedthebot.com/tools/headers/test.php

https://www.directtraveller.com/holidays/about-direct-traveller/british-travel-awards.asp

HTTP/1.1 **302 Found **
Server: nginx/1.6.0
Date: Sat, 11 Apr 2015 02:59:23 GMT
Content-Type: text/html; charset=iso-8859-1
Connection: keep-alive
Location: https://www.directtraveller.com/awards

Header transfer size: 199

http://www.directtraveller.com/holidays/about-direct-traveller/british-travel-awards.asp

301 Moved Permanently

https://www.directtraveller.com/holidays/about-direct-traveller/british-travel-awards.asp

302 Found

|

you can convert Htaccess to nginx using this tool http://winginx.com/en/htaccess

however I would force SSL instead of use a rewrite through the converter. The redirects below work but I would use the server-side redirect labeled use this

Check out Engine Yard for more redirects I have placed quite a few here

https://blog.engineyard.com/2011/useful-rewrites-for-nginx

this is a basic redirect you can put the port or each port in place.

server {
server_name example.com;
rewrite ^/(.*) https://example.com/$1 permanent;
}

USE THIS

Redirect both, non-SSL and SSL to their www counterpart:

<code>**server {
    listen 80;
    listen 443 ssl;
    server_name directtraveller.com;
    return 301 $scheme://www.directtraveller.com$request_uri;
}**

server {
    listen 80;
    listen 443 ssl;
    server_name example.com;
    # rest goes here...
}</code>

Add a www with this block

server {
listen 80;

listen 443 ssl;

server_name directtraveller.com;
rewrite ^(.*)$ $scheme://www.directtraveller.com$1;
}

(

)

Remove a www with this block instead

server {
listen 80;
server_name www.directtraveller.com;
rewrite ^(.*)$ $scheme://directtraveller.com$1;
}

<code>rewrite ^(.*)$ https://$host$1 permanent; #3
rewrite ^ https://$host$request_uri permanent; #4

I**f you have any questions please feel free to ask I hope this is enough information and not overwhelming. If you feel overwhelmed simply use the very first config.**

 **Sincerely,**
 **Tom**</code>

TheWebMastercom

What did you put to redirect the following:

https://www.directtraveller.com/holidays/about-direct-traveller/british-travel-awards.asp
to
https://www.directtraveller.com/awards

As that is where the problem lies.

Direct_Ram

John threw that in and did a retest and is working now - you genius! Thanks

RyanPurkey

Hi Ram. If Jon's fix above doesn't work, you might want to post the link(s) you're testing with Screaming Frog so that people here can see what's going on and give you specific recommendations. It sounds like there's a 302 in place on the http version of your site, but people will need details to see where exactly. Cheers!

TheWebMastercom

Try this in your .htaccess file:

RewriteCond %{HTTPS} off

First rewrite to HTTPS:

Don't put www. here. If it is already there it will be included, if not

the subsequent rule will catch it.

RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

Now, rewrite any request to the wrong domain to use www.

RewriteCond %{HTTP_HOST} !^www.
RewriteRule .* https://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

Welcome to the Q&A Forum

Browse the forum for helpful insights and fresh discussions about all things SEO.

Moz Q&A is closed.