Recursive URL error

We have rewritten our website using the Xara Web Designer Premium and when we replace our legacy site with the Xara version we see the following issue:

-) we point the Microsoft IIS to the legacy folder containing our index.htm file
-) we open a browser on another system and enter www.mydomain.com
-) all works well
-) we delete all of the files in the legacy folder and replace them with the files exported by Xara
-) we open a browser on another system and enter www.mydomain.com
-) the URL immediately goes to http://www.mydomain.com/www.mydomain...w.mydomain.com....
-) this recursion ends with the browser issuing an error
-) when we copy the legacy files back, the site works again

We are sure there is a basic issues we are overlooking, any help would be appreciated.

Sounds like the .htaccess file or IIS equivalent is still in place and has not been purged. Try publishing to a different location.

Acorn

Acorn,

Thanks, just tried pointing IIS to a new directory and that did not resolve this issue.

I am confused as to what purpose the IIS is doing in your environment.
As I recall from aeons back, IIS takes .aspx files and renders html from there.

Is this the case with your old site?
If so, would changing the filename in your XDA of index to index.aspx possibly work?

The Xara HTML Filter renders static code so unless you have a full IIS managed environment I don't see the purpose of it at all.

Acorn

We have solved the issue with a temporary hack.

We use IIS Servers for all of our WEB sites and have no plans to abandon them. In the past we had always used Microsoft Front Page or Adobe Dream Weaver with no issues. Our goal was to try Xara out as a possible drop-in candidate for a WYSIWYG WEB Site authoring tool. Given the support we have received to date, we may end up abandoning Xara and looking to other vendors.

So Xara gets damned without any indication as to how it causes the issue or your hack. Xara's HTML is agnostic to the type of web server as it is static code with no external dependencies. I have embedded many sites into MS environments including SharePoint, the only one that did not like a particular filename and extension. Never a recursion error that was not caused by a misconfiguration of the environment, a thing a Xara design is incapable of.

Acorn