364132 - [Regression] Is setting the document.domain property one-time-only ?

Status: RESOLVED DUPLICATE of bug 148142

(Firefox :: General, defect)

Description

[wonesek]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1) Gecko/20061010 Firefox/2.0

Hello,

First, take a look at : https://bugzilla.mozilla.org/show_bug.cgi?id=290100 because i think this is the same bug.

I was reading this : 

http://fettig.net/weblog/2005/11/30/xmlhttprequest-subdomain-update/
&
http://www.fettig.net/weblog/2005/11/28/how-to-make-xmlhttprequest-connections-to-another-server-in-your-domain/

So, since ff > 1.5, you have fixed this problem, but when i try this test :
http://fettig.net/playground/ajax-subdomain/test3.html

it doesn't work anymore under ff 2.0.

Sorry if it's short but my english isn't very well :)

Bye.

Reproducible: Always

Comment 1

[wonesek]

Here is the error i get :

Erreur : [Exception... "Illegal document.domain value"  code: "1009" nsresult: "0x805303f1 (NS_ERROR_DOM_BAD_DOCUMENT_DOMAIN)"  location: "http://www.fettig.net/playground/ajax-subdomain/test3-iframe.html Line: 10"]
Fichier source : http://www.fettig.net/playground/ajax-subdomain/test3-iframe.html
Ligne : 10

Comment 2

[Jesse Ruderman]

This sounds a lot like bug 148142, but you said this is a regression, so I'm not marking it as a dup yet.

Comment 3

[Ria Klaassen (not reading all bugmail)]

Your testcase does not work in a Windows trunk build of 26 August 2005, so it's not the same bug or the fix does not work. 

Comment 4

[Daniel Veditz [:dveditz]]

bug 290100 remains fixed. That was fixing an issue where document.domain should not affect whether XHR worked or not.

Starting on a page at http://www.mozilla.com
<script>
  document.domain = "mozilla.com";
  x = new XMLHttpRequest();
  x.open('GET',"http://mozilla.com/",true);      // error!
  x.open('GET',"http://www.mozilla.com/", true); // works

Not sure why the fettig testcase is failing, but not bug 290100. (Note, the page expects Firefox to fail.) It does sound like a dupe of bug 148142, and the exception from resetting to www.fettig.net aborts the script before the setTimeout() can set up the loop.