You may be able to work around it in the interim by using a client-side redirect (meta refresh); I _think_ that won't set the originalURI to anything untoward, unlike this case.
Could you explain this a little, I don't know what you mean here.
What happens is that on HTTP redirects Mozilla keeps track of the "original" URI (the URI that was initially requested) as well as of the "actual" URI (the post-redirect URI). The XUL Document code was using the "original" URI, incorrectly, instead of the "actual" URI to resolve relative URIs.
If the redirect is done via <meta http-equiv="Refresh">, I don't believe we keep track of the "original" URI, so this problem should not be hit.
I appear to have a bugzilla account. I don't remember creating it.
That happens. ;) Please do cc me on the bug...
I have created a new version of the moztest.jar here:
jar:https://secure.arcamax.com/moztest/moztest.jar!/test.xul
https://secure.arcamax.com/moztest/moztest.jar is a 404....
-Boris _______________________________________________ Mozilla-netlib mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-netlib
