Tag Info

New answers tagged

0

Just think about the customer... A one page, dedicated site with information about each dealer is going to please visitors/customers more so than them simply redirecting to your general site. When I put it in that context, it's easy to understand that they should have a one-page site as a 'make do' rather than a 301 redirect.


-1

It also depends on Competition. For example, I saw 2-3 sites from the 2th page in google.gr with https to come on 1th page. As Google says it has affected 1% till now.


1

I think the following mod_rewrite directives should do what you require, however, whether they do anything at all may be dependent on your configuration. RewriteEngine on RewriteCond %{QUERY_STRING} rsform RewriteRule ^joomla/(.+)$ http://watervriendengeleen.nl/formulieren/$1 [L,R=301] This redirects all requests for files in your /joomla/ subfolder, ...


1

Perfectly fine to 301 redirect all HTTP pages to their HTTPS equivalent. Either via httpd.conf on Apache servers, .htaccess rewrites or with a PHP include like your example. Any inbound links would pass about 97% of weight through a 301 redirect. The best handling internally would be to not use the protocol for internal linkage so that compatibility is ...


1

If they want content on the sites they own they should put unique content on it. One page is enough. Much better than 302ing to your site.


3

For your first two rewrites (non-www → www, http → https), the following rule should work: RewriteEngine On RewriteCond %{HTTPS} off [OR] RewriteCond %{HTTP_HOST} !=www.example.com [NC] RewriteRule ^(.*) https://www.example.com/$1 [NS,L,R=permanent] Just replace www.example.com with the actual canonical hostname of your site. As for your third ...


1

I need to double check the specifications, but I am pretty certain that cached objects depend on the request method. So an object using HTTP would be a different cache entity from HTTPS. So if you are redirecting to HTTPS, there should be no prior cache data. Also, you may want to consider using lower cache periods and requiring validation prior to ...


0

You can log into google webmaster tools and re-index your site. Found that is speeds up the process.


0

Just try editing .htaccess file. Just paste the following code in .htaccess file #Force www: RewriteEngine on RewriteCond %{HTTP_HOST} ^example.com [NC] RewriteRule ^(.*)$ http://www.example.com/$1 [L,R=301,NC] replace "example" with "your domain name".


1

I don't know about GoDaddy's error, other than maybe it is expecting example.com rather than www.example.com (although I doubt it)?! You don't actually need to specify the host if redirecting on the same site? But anyway, this is easy to do in your root .htaccess file using mod_alias: Redirect 301 /oldpage.html /new-page.html (This assumes Apache 2.2.6+ ...


1

Would this be done on the internal IIS web server I assume you're using IIS. It's possible with IIS. There are several ways. I will show the way where you use the web.config file. In your web.config file put the following code: <rewrite> <rules> <rule name="Redirect domain.com to www" patternSyntax="Wildcard" ...


1

I am assuming that you still want requests that look like: http://www.parsilatex.com/joomla/index.php/1391-09-23-16-04-58 ...to still work. If this is not the case, please leave a comment and I will update the answer. I have not tested this here, but try: RewriteEngine On RewriteCond %{REQUEST_URI} $/joomla/index\.php^ [NC] RewriteRule .* ...


1

I had to ask this question myself. It is surprisingly tricky to do. Olaf Dietsche provided the solution of using an environment variable: RewriteRule ^contact$ contact.php [L,E=CLEAN_CONTACT_URL:1] RewriteCond %{ENV:REDIRECT_CLEAN_CONTACT_URL} !1 RewriteRule ^contact\.php$ /contact [R=301,L] That way the redirect only gets executed when contact.php is ...


1

You have two choices. You allow Internet traffic on port 443 on the machine within the internal network. Something your sysadmins might now want you to. If you don’t have sysadmins, please don’t :) Re-use another already server already exposed to the Internet. This is what we call a "Proxy", a fancy term to say "server for". There are many ways to ...


0

You are mixing the mod_alias and mod_rewrite modules, which means that the end result is often unexpected. You should only use mod_rewrite in your case, that is, repöace your Redirect 301 /contact.php http://www.example.com/contact with RewriteRule contact.php http://www.example.com/contact [R=301,L] And then, as Dave mentioned, you should use the [L] ...


0

Use the [L] flag on your rewrite rule and place your redirect before it. (I'm going to use a rewrite here as well) RewriteRule ^/contact\.php$ http://www.example.com/contact [R=301,L] RewriteRule ^contact$ /contact.php [L] When the first rule is encountered it matches the /contact.php request and is the last rule processed. The redirect to /contact does ...


1

Yes you would. You are telling Apache to take any reference to contact and rewrite the URI to contact.php then telling Apache to take any contact.php reference and change it to /contact which gets captured again by the first rule. Here is what you are missing. For each rewrite or redirect, Apache makes the change then starts the whole matching process over ...


1

This should do it. RewriteEngine On RewriteRule social(.*) https://twitter.com$1 [R=301,L]



Top 50 recent answers are included