Opened 11 years ago
Last modified 4 years ago
#10691 assigned defect
windowName transport is not working on HTTPS to HTTP configuration using FireFox
Reported by: | jamoville | Owned by: | dylan |
---|---|---|---|
Priority: | high | Milestone: | 1.15 |
Component: | Dojox | Version: | 1.4.0 |
Keywords: | windowname | Cc: | |
Blocked By: | Blocking: |
Description
dojox.io.windowName.send fails to POST data when the local host is https and the remote host is http in Firefox. I believe this is happening because FireFox? is displaying a warning message to the user about sending unencrypted data from an encrypted site. FireFox? uses the about:blank location while waiting for the user’s input to this warning message. The windowName transport then tries to navigate back to the local domain and grab the data out of about:blanks’s window name, which doesn’t exist . I think this is a simple fix. It looks like this case is already handled for every browser except FF
Take a look at the following code from windowName’s onload function:
if(!dojo.isMoz && frame.contentWindow.location =='about:blank'){
opera and safari will do an onload for about:blank first, we can ignore this first onload
return;
}
I think all that needs to be done here is to remove the isMoz condition.
if(frame.contentWindow.location =='about:blank'){
opera and safari will do an onload for about:blank first, we can ignore this first onload
return;
}
OS - Windows Browser version - Firefox 3.5 Dojo Build - 1.2.3
Change History (3)
comment:1 Changed 11 years ago by
Component: | General → Dojox |
---|---|
Owner: | changed from anonymous to Kris Zyp |
comment:2 Changed 5 years ago by
Milestone: | tbd → 1.12 |
---|---|
Owner: | changed from Kris Zyp to dylan |
Status: | new → assigned |
comment:3 Changed 4 years ago by
Milestone: | 1.13 → 1.15 |
---|
Ticket planning... move current 1.13 tickets out to 1.15 to make it easier to move tickets into the 1.13 milestone.