HTTPS AJAX DOJO, responds with HTTP

[GoogleCodeExporter]

What steps will reproduce the problem?
1. I'm including the DOJO ajax libraries using HTTPS protocol
<script type="text/javascript" 
src="https://ajax.googleapis.com/ajax/libs/dojo/1.3.1/dojo/dojo.xd.js" 
djConfig="parseOnLoad: true"></script>

2. The broser reports that the site is insecure, becouse contents are 
loaded from NOT HTTPS site.

Detalles de error de página web

Agente de usuario: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; 
Trident/4.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; InfoPath.2; 
MS-RTC LM 8; OfficeLiveConnector.1.3; OfficeLivePatch.0.0; .NET CLR 
3.5.30729; .NET CLR 3.0.30618)
Fecha: Tue, 16 Jun 2009 22:07:56 UTC

Mensaje: Could not load 'dijit.form.ValidationTextBox'; last tried 
'http://ajax.googleapis.com/ajax/libs/dojo/1.3.1/dijit/form/ValidationTextB
ox.js'
Línea: 16
Carácter: 5295
Código: 0
URI: https://ajax.googleapis.com/ajax/libs/dojo/1.3.1/dojo/dojo.xd.js

Mensaje: Excepción lanzada y no recogida
Línea: 16
Carácter: 16920
Código: 0
URI: https://ajax.googleapis.com/ajax/libs/dojo/1.3.1/dojo/dojo.xd.js

What is the expected output? What do you see instead?
The expected is that the libraries must coexist in the same protocol.

What version of the product are you using? On what operating system?
DOJO 1.3.1, depending the restrictions the site fail or show warnings.

Original issue reported on code.google.com by egar...@gmail.com on 16 Jun 2009 at 10:17

[GoogleCodeExporter]

The problem is that registerModulePath within the dojo file sets each module 
path to 
the http domain. The problem may come from the dojo build process. If the 
parameter xdDojoPath is set to the full domain, with the "http" protocol, then 
this will be used 
for the ModulePaths within the dojo file itself. Thus even if you refer to the 
https 
root file, or even use the google loader, when the dojo file itself loads it 
will point  
the other module namespaces back to the http URL.

Original comment by sean.ne...@gmail.com on 17 Jun 2009 at 7:19

[GoogleCodeExporter]

Original comment by jscud.w...@gmail.com on 28 Jul 2010 at 1:15

• Added labels: APIType-Libs

[GoogleCodeExporter]

I noticed another HTTP/HTTPS crossover problem with the jquery api.

When using:

  <script src="https://www.google.com/jsapi"></script>
  <script>google.load("jquery", "1",null);</script>

the jsapi makes a call to http://www.google.com/uds/stats?r0=el%7Cjquery&nc=... 
(for usage tracking purposes?) which causes the browser to report that the site 
is not fully secure (mixed http/https).  The jsapi could/should use https in 
that uri in this case.

Original comment by displague on 4 Aug 2010 at 3:34