12-15-2012, 09:47 AM
I've been tracking down the cause for some problems I'm having with the KittyCatS web site. I think I've found it, but there may be additional places where the mistake was made.
When switching from one user account to another the login process sends a web-page redirect along with a web page.
The redrect is to the web domain http://www.kittycats.biz, as is the link on the page sent with the redirect.
Everywhere else (that I've found) the pages are in the kittycats.biz domain.
This confusion between the domains is the problem.
Would it be possible to have the HTTP REDIRECT and the web page service with it corrected to use the proper web domain: kittycats.biz?
For what I'm doing, I'm pretty sure I can cobble together a workaround which (mostly) corrects the error. But it's a slimy hack and it would be much better to have the web pages in a consistent web domain.
Actually, on my side, the hack wasn't that slimy. Any time I see a web page in the http://www.kittycats.biz web domain I immediately reload the page from the http://kittycats.biz web domain. It's almost unnoticable on the screen, but it doubles up the web traffic for first page served from the incorrect domain. Luckily, it only happens a few places and, once corrected, it says corrected until the next time the user hits the error in the web server.
When switching from one user account to another the login process sends a web-page redirect along with a web page.
The redrect is to the web domain http://www.kittycats.biz, as is the link on the page sent with the redirect.
Everywhere else (that I've found) the pages are in the kittycats.biz domain.
This confusion between the domains is the problem.
Would it be possible to have the HTTP REDIRECT and the web page service with it corrected to use the proper web domain: kittycats.biz?
For what I'm doing, I'm pretty sure I can cobble together a workaround which (mostly) corrects the error. But it's a slimy hack and it would be much better to have the web pages in a consistent web domain.
Actually, on my side, the hack wasn't that slimy. Any time I see a web page in the http://www.kittycats.biz web domain I immediately reload the page from the http://kittycats.biz web domain. It's almost unnoticable on the screen, but it doubles up the web traffic for first page served from the incorrect domain. Luckily, it only happens a few places and, once corrected, it says corrected until the next time the user hits the error in the web server.