1. We use apache and the domain is set up in httpd.conf to load a page in an area of our site separate from the rest of the site using virtual hosting.
2. The page that actual loads is just a frameset command:
<html>
<head>
<title>This is the title</title>
</head>
<frameset framespacing="0" border="0" rows="*,0" frameborder="0">
<frame name="Frame1" noresize scrolling="auto"
src="http://www.blue-widgets.org/campaigns/index.html">
<frame name="Frame2" scrolling="no" noresize>
</frameset></html>
and [blue-widgets.org...] is the page on our actual site.
On a few of these pages on our real site, I've had to add a framebreaking command:
<SCRIPT LANGUAGE="JAVASCRIPT">
<!----
if (top.frames.length > 1) {
top.location="http://www.blue-widgets.org/campaigns/index.html";
}
// -->
</SCRIPT>
This is because if I didn't break the page out of the frame, it would obscure the security padlock in the lower right hand of the screen when people followed links to our payment processor.
But now I am getting complaints from frame-using sites that link to us that when they link to our domain, which is just a frameset command that loads a frame-breaking page, it is impossible for people to use the back button to return to the site they came from. The back button just goes back to our frameset page, which reloads the frame-breaking page.
This is all pretty complicated, but is there some better solution than:
1. Telling people to link to the real page, not the frameset domain (not practical).
2. Using a javascript redirect.
I also should mention the reason we use the domain with the frameset. If we set up a functioning domain separate from our site, the Server Side Includes wouldn't work.
DaveN
