I have an XSL/XML transform setup, and it was working fine until my server changed IP addresses, now it's either reporting it's generic error

Either the XML or XSL data specified for this transform is an invalid URL, or the remote document is unavailable.

Or when I reload the page, it's hanging for minutes at a time, occasionally reporting a runtime error.

The code on my sever hasn't changed at all since it was working, and I can access the XSL file, and the CGI script that generates the XHTML file from outside my network.  The address has been changed for over 12 hours now.

Even if I change the address of the page to refer to IP address directly in the XML/XSL Transformation Editor it still displays this information.

Does the system cache the XML file it downloads for a certain time before it fetches it again?  I am seeing no connection attempts to my machine for the referenced documents at all.

What's going on here?

No, it's the exact same machine, just a new net card, so my ISP gave it a new IP address (DHCP binds to MAC address for my ISP)

Here are the 2 files that I'm using for the transform.

http://pawz.cattech.org/goc/index.cgi?xml=1
http://pawz.cattech.org/goc/tbl.xsl

If I take the source of those addresses, and run them through xsltproc on my linux box, I do get the expected output.  The thing that wierds me out is that guildportal will hang for long periods of time on the pages with the transform.

name="2911178">

I know that this is an old thread, and hasn't been posted to in over a month, but i am having a problem with my xml/xsl transforms.  this problem occured shortly after Mythc launched its new expansion.  I was wondering if any other DAoC guilds where experiencing this problem, or if it is just local on my site Church of mithra

Any XSL markup that uses the servers.xml file has been broken since the release of NF. This is due to the fact that the XML is now malformed in the Mordred section of the XML where there is no end tag for each of the relics. (No after each of the entries) I've posted to the Herald hoping that they will fix it, but no change yet.

I've also posted the details here. Feel free to drop the folks at the Herald a message about it. Hopefully they can fix this soon. There are a bunch of problem sections on our website until they get this corrected.