htaccess not allowing login in 3 of 4 miva shopping carts

what could be causing it?

[Lorel]

I have had 3 Miva shopping carts set up for clients on the same host and working (and installing a new one) and now all of a sudden I can't log into three of them including the newest one. They all had simple 301 redirects to fix the split domain problem in htaccess after the shopping carts were set up and I was able to log into the last 3 in last few months with no problem so the problem has occured since my last login (Probably some "improvement" they made that is messing up Miva).

The host tech is claiming it's the htaccess file messing up the logins but I logged into 2 of the ones that aren't working within the last 2 months and haven't touched the sites since.

Here is a sample htacess file. I use this on about 30 client sites and I have tested all 3 items below on all 3 sites and they are working fine.

ErrorDocument 404 /missing.html
AddHandler server-parsed .html

Options +FollowSymLinks
RewriteEngine on
RewriteCond %{HTTP_HOST} ^domainnamegoeshere\.com
RewriteRule ^(.*)$ [domainnamegoeshere.com...] [R=301,L]

Anyone know why this would prevent a shopping cart login?

[jdMorgan]

1) Is this the only code in .htaccess?
2) Have you removed the code and verified that the login works without it?
3) Have you checked to see what domain the login is expecting? It is possible that logging in requires you to use the no-www domain, and I've seen a few cases where logins actually required the IP address to be used.

If you can identify this as the cause, then adding a simple exclusion to disable the domain rewrite for login pages would fix it.

Jim

[Lorel]

Hi JD,

>1) Is this the only code in .htaccess?

It is on the one site.

>2) Have you removed the code and verified that the login works without it?

The tech person did so.

>3) Have you checked to see what domain the login is expecting? It is possible that logging in requires you to use the no-www domain, and I've seen a few cases where logins actually required the IP address to be used.

The login is any name I choose. However it's the SSL certificate that is causing the problem, which I forgot to mention. Maybe that needs a different set up.

>If you can identify this as the cause, then adding a simple exclusion to disable the domain rewrite for login pages would fix it.

Ok, I'll check. Can you explain how to do this?

thanks,

[jdMorgan]

Your SSL cert needs to match the 'realms' or 'domains' that it's used in, and that sounds like the problem.

Jim

[Lorel]

After much research I found the correction for this problem. Being as thousands of people use Miva someone else might want this info:

To ALLOW MIVA LOGIN AND SLL TO WORK WITH 301 Redirect
use this command (CHANGE IP ADDRESS)
Make sure you add it before the other RewriteCond and RewriteRule entries.
USE the IP address to the Shared SSL, not the domain IP.

Options +FollowSymLinks
RewriteEngine on
RewriteCond %{REMOTE_ADDR}!^Put.SSL.IP.Address.Here$
RewriteCond %{HTTP_HOST} ^domain\.com
RewriteRule ^(.*)$ [domain.com...] [R=301,L]