If I create a webpage in DotNetNuke, and I point to an html page that is stored in DMX using the WebDav formatted URL, (i.e. www.mysite/dmxdav.axd/path/to/file.html), then IIS serves the web page, and I can see it just fine.

If I reference a JPG file using a relative reference from within file.html, say "images/picture.jpg", then IIS says the file can not be found.  I get the same 404 message if I try to access "http://www.mysite/dmxdav.axd/path/to/images/picture.jpg".  Does this have something to do with the configuration of MIME types in IIS, or something to do with the way DMX handles GET requests.

I notice that there is a free app on this site which expands saved mhtml archives into a particular module.  I would guess that the resulting archive can not be stored in DMX for this reason.  But maybe there's a workaround?  I'm basically trying to decide on the best way of archiving web reference material, and I thought storing the files in DMX presented a versatile way of doing so; but if I can't view the saved file via the web, then I may have to change my approach.

Thanks.