1101506 - Firefox version 33.1 doesnt load Google maps api V3 javascript file over https

Status: RESOLVED INVALID

(Firefox :: Untriaged, defect)

Description

[Hari]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.59 Safari/537.36

Steps to reproduce:

I am using Firefox version 33.1 and trying to generate google maps using google maps javascript api V3 over https/SSL. 

The core issue can be reproduced by hitting the test google maps url:-
https://google-developers.appspot.com/maps/documentation/javascript/examples/full/map-simple

The same application code is functioning as expected in IE and chrome.
This issue is occurring only while importing the google maps js over https protocol
Js Import :- https://maps.googleapis.com/maps/api/js?v=3.exp
Issue has been replicated over multiple n/ws and machine over the latest version of Firefox.


Actual results:

The maps dont get loaded and an error is logged in the console as 
"ReferenceError: google is not defined".
Debugging in javascript shows that the google javascript object is undefined.


Expected results:

The google javascript object should get loaded and the maps should get displayed.

Comment 1

[Loic]

WFM with FF33.1, see http://i.imgur.com/op1SZQJ.jpg

Could you test with a clean profile, please.
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

In that fails, type about:support in the location bar and paste the "graphics" section.

Comment 2

[Hari]

Hi Loic,

I did delete my existing profile and try it out.Still doesnt work. The graphics section you wanted:-
Adapter Description	RDPDD Chained DD
Adapter Description (GPU #2)	Citrix Display Driver (Citrix Systems - WDDM)
Adapter Drivers	RDPDD
Adapter Drivers (GPU #2)	vd3d vd3d32
Adapter RAM	Unknown
Adapter RAM (GPU #2)	8
Device ID	0x0000
Device ID (GPU #2)	0x0405
Direct2D Enabled	Blocked for your graphics card because of unresolved driver issues.
DirectWrite Enabled	false (6.2.9200.16492)
Driver Date (GPU #2)	11-26-2013
Driver Version (GPU #2)	6.3.400.13
GPU #2 Active	false
GPU Accelerated Windows	0/1 Basic (OMTC) Blocked for your graphics card because of unresolved driver issues.
Vendor ID	0x0000
Vendor ID (GPU #2)	0x15ad
WebGL Renderer	Blocked for your graphics card because of unresolved driver issues.
windowLayerManagerRemote	true
AzureCanvasBackend	skia
AzureContentBackend	cairo
AzureFallbackCanvasBackend	cairo
AzureSkiaAccelerated	0

Comment 3

[Hari]

Maybe this helps:-
I see 2 407 errors for the url https://maps.googleapis.com/maps/api/js?v=3.exp with messages Proxy Authentication required, before the request goes thru with a 200 response code.
In Chrome, this request gets completed in one time.

Comment 4

[:Gijs (he/him)]

(In reply to Hari from comment #3)
> Maybe this helps:-
> I see 2 407 errors for the url
> https://maps.googleapis.com/maps/api/js?v=3.exp with messages Proxy
> Authentication required, before the request goes thru with a 200 response
> code.
> In Chrome, this request gets completed in one time.

This sounds like Firefox is behind a proxy? Can you provide whatever details you can about the proxy, the request/response headers for the 3 requests (2 failing, 1 succeeding) in Firefox, and a comparison with the 1 succeeding request in Chrome?

Also, if the request goes through the 3rd time, why is it not working?

Are all the machines behind the same proxy?

Comment 5

[Hari]

I'll send in the request details as soon as possible.
I am not really sure on why its failing for the initial 2 times, why its going through the 3rd time and why it doesnt work even after that.
As for the second question, indeed firefox, chrome and IE are all operating behind the same proxy. So I would really expect the same behavior across all the 3 browsers, but strangely thats not the case.

Comment 6

[Hari]

Below is the request/response header information as required. 
The 1st is from Chrome
The 2nd is from the failing request in Firefox. There is one more such request, but I have skipped that over here
The 3rd is from the successful request in Firefox. Even after this the map is not displayed.

Header information in chrome:-
Request:
Accept:*/*
Accept-Encoding:gzip,deflate,sdch
Accept-Language:en-US,en;q=0.8
Cache-Control:max-age=0
Connection:keep-alive
Cookie:BCSI-CS-989185c5f1ad1a4f=2
Host:maps.googleapis.com
Referer:https://google-developers.appspot.com/maps/documentation/javascript/examples/full/map-simple
User-Agent:Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.59 Safari/537.36
Response:
Age:0
Alternate-Protocol:443:quic,p=0.01
Cache-Control:public, max-age=1800
Connection:Keep-Alive
Content-Encoding:gzip
Content-Type:text/javascript; charset=UTF-8
Date:Thu, 20 Nov 2014 09:11:10 GMT
Expires:Thu, 20 Nov 2014 09:41:10 GMT
Server:mafe
Transfer-Encoding:chunked
Vary:Accept-Language
X-Frame-Options:SAMEORIGIN
X-XSS-Protection:1; mode=block
---------------------------------------------------------------------------------------------
Failure Header information in Firefox:-
Request:
Host:"maps.googleapis.com"
User-Agent:"Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0"
Accept:"*/*"
Accept-Language:"en-US,en;q=0.5"
Accept-Encoding:"gzip, deflate"
Referer:"https://google-developers.appspot.com/maps/documentation/javascript/examples/full/map-simple"
Connection:"keep-alive"
Response:
Cache-Control:"no-cache"
Connection:"close"
Content-Length:"804"
Content-Type:"text/html; charset=utf-8"
Pragma:"no-cache"
Proxy-Authenticate:"NEGOTIATENTLM"
Proxy-Connection:"close"
---------------------------------------------------------------------------------------------
Success Header information in Firefox:-
Request:
Host:"maps.googleapis.com"
User-Agent:"Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0"
Accept:"*/*"
Accept-Language:"en-US,en;q=0.5"
Accept-Encoding:"gzip, deflate"
Referer:"https://google-developers.appspot.com/maps/documentation/javascript/examples/full/map-simple"
Connection:"keep-alive"
Proxy-Authorization:"Negotiate TlRMTVNTUAADAAAAGAAYAIAAAAAYABgAmAAAAAgACABYAAAADgAOAGAAAAASABIAbgAAABAAEACwAAAAFQKI4gYBsR0AAAAPeXlYB0Y7M35DwOFsdw/oQFYARQBSAFoAOQAzADEANQA3ADgAMQBWAEQAVAAwADEAMAAwADgAMADBUGgZugDHxAAAAAAAAAAAAAAAAAAAAAB4DfF1VcBI8u8wiVTuBLqgW+v11BSHeGl/qrXMHCO+6/DNoEM+U0W2"
 
Response:
No response comes thruough.

Comment 7

[Hari]

Gentelmen,

After a lot of debugging, we seem to have found a root cause.
The issue is a proxy configuration within a specific n/w in the organization that is blocking these requests.
Thanks a lot for your assistance and time.