1023742 - [BROWSER] Error message is not displayed if you try to open http://aaaa.mozilla.org

Status: VERIFIED INVALID

(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect)

Description

[rafael.marquez]

*Branch 2.0

*Procedure
1. Open browser app
2. Try to open the web page http://aaaa.mozilla.org

*Expected Result
A error message is displayed

*Actual Result
The page is displayed in blank and error message is not displayed

Comment 2

[Jason Smith [:jsmith]]

Oh wait I see now - this is actually a deeper level problem that's preventing analysis of bug 1022433.

Comment 3

[Duane Dixon [:ddixon]]

(In reply to rafael.marquez from comment #0)
> *Branch 2.0
> 
> *Procedure
> 1. Open browser app
> 2. Try to open the web page http://aaaa.mozilla.org
> 
> *Expected Result
> A error message is displayed
> 
> *Actual Result
> The page is displayed in blank and error message is not displayed

What kind of error message should be displayed?

I am getting the same results described in bug 1022433.  

I'm trying to understand what I should be seeing in a non-broken build that displays the correct "error message" when the browser cannot connect to a web address. 

If you could provide the device and the build number that this was reproduced on, would be helpful.  Thanks!

Comment 4

[Albert [:albert]]

(In reply to ddixon from comment #3)
> (In reply to rafael.marquez from comment #0)
> > *Branch 2.0
> > 
> > *Procedure
> > 1. Open browser app
> > 2. Try to open the web page http://aaaa.mozilla.org
> > 
> > *Expected Result
> > A error message is displayed
> > 
> > *Actual Result
> > The page is displayed in blank and error message is not displayed
> 
> What kind of error message should be displayed?
> 
> I am getting the same results described in bug 1022433.  
> 
> I'm trying to understand what I should be seeing in a non-broken build that
> displays the correct "error message" when the browser cannot connect to a
> web address. 
> 
> If you could provide the device and the build number that this was
> reproduced on, would be helpful.  Thanks!

We don't see any error message, just a blank page.

Device: hamachi
Build ID: 20140611203026
Gaia: b36d7d43f9c610def965ed7dba88219101aee073
Gecko: 41a8e5ba9270c1fe4b99c8e62b97d065dbf51dd8
Version: 31.0a1 (Master)

Comment 5

[Jason Smith [:jsmith]]

My guess is that this is occurs on devices with the same resolution as Buri, but not Flame. Can we try reproducing on Buri?

Comment 6

[Albert [:albert]]

The problem seems to happen with mobile connection. Hamachi using wifi shows the error page but using mobile data 3g shows blank page.

Comment 7

[Duane Dixon [:ddixon]]

Unable to reproduce a blank error screen on a Buri (Hamachi) device. 

Buri Results for an "H" and "E" device: Attempting to access an invalid website

wifi off, data off-- "Unable to connect" error 

wifi on, data off-- "Server not found"  error

wifi off, data on-- "Server not found" error

poor wifi signal, data off-- "Server not found" error

Airplane mode on-- "Unable to connect" 

Environmental Variables:
Device: Buri 2.1 - Master
Build ID: 20140611184732
Gaia: 41db6954a67efc55016744bc8f6591ae9e07a285
Gecko: 9e8e3e903484
Version: 33.0a1 (2.1 - Master) 
Firmware Version: v1.2device.cfg

Comment 8

[:gerard-majax]

Rafael, what build were you using exactly?

I do confirm that I'm unable to reproduce the issue myself on a Flame running master. Do you mind checking on your side?

Comment 9

[Marcelino Veiga Tuimil [:sonmarce]]

I can reproduce it in today build for hamachi and connected vi WiFi

Comment 10

[Marcelino Veiga Tuimil [:sonmarce]]

I made a mistake, please, forget comment 9

Comment 11

[Marcelino Veiga Tuimil [:sonmarce]]

As indicated in comment 6, the problem only happens when connected via 3G. And I was able to reproduce it  the test with today build of hamachi and connected via 3G.

Comment 12

[:gerard-majax]

(In reply to Marcelino Veiga Tuimil [:sonmarce] from comment #11)
> As indicated in comment 6, the problem only happens when connected via 3G.
> And I was able to reproduce it  the test with today build of hamachi and
> connected via 3G.

Sorry to ask such a dumb question, but this makes me wondering of one thing: are you sure the 3G network returns you a proper error ?

Comment 13

[Marcelino Veiga Tuimil [:sonmarce]]

I do not understand what you mean, 3G network is working, as I can browse existing server pages

Comment 14

[:gerard-majax]

(In reply to Marcelino Veiga Tuimil [:sonmarce] from comment #13)
> I do not understand what you mean, 3G network is working, as I can browse
> existing server pages

Considering what telcos are doing with 3G, I would not consider their network to be trustworthy. Please check that you get a proper dns error.

Comment 15

[Marcelino Veiga Tuimil [:sonmarce]]

Just tested with 1.3 and got same behavior, we are going to check if there is a problem with operator network

Comment 16

[:gerard-majax]

(In reply to Marcelino Veiga Tuimil [:sonmarce] from comment #15)
> Just tested with 1.3 and got same behavior, we are going to check if there
> is a problem with operator network

Running tcpdump on the device will help you.

Basically, you want to |tcpdmp -s0 -iany -w /mnt/sdcard/bug1023742.pcap port 53 or port 80|. What we expect is that the DNS request will return NXDOMAIN.

If it returns NXDOMAIN and you still see the issue, then it may be a legit bug on Gecko or Gaia side.

Comment 17

[Albert [:albert]]

Attachment: 3g.pcap

Tcpdump output when opening http://www.aaaa.yh with 3G connection.

Comment 18

[Albert [:albert]]

Attachment: wifi.pcap

Tcpdump output when opening http://www.aaaa.yh with wifi connection.

Comment 19

[Albert [:albert]]

I attached the tcpdump result of trying to open the url http://www.aaaa.yh using wifi and 3G.

As you can see, when going by wifi there are several queries for www.aaaa.yh to the DNS server and it responds with a 'no such name' found.

On the other hand, when going by 3G we have a TCP stream:

request:  GET http://aaaa.yh/ HTTP/1.1
response: HTTP/1.1 503 Service Unavail

Comment 20

[:gerard-majax]

(In reply to Albert [:albert] from comment #19)
> I attached the tcpdump result of trying to open the url http://www.aaaa.yh
> using wifi and 3G.
> 
> As you can see, when going by wifi there are several queries for www.aaaa.yh
> to the DNS server and it responds with a 'no such name' found.
> 
> On the other hand, when going by 3G we have a TCP stream:
> 
> request:  GET http://aaaa.yh/ HTTP/1.1
> response: HTTP/1.1 503 Service Unavail

In which case I would say there is no bug :)

Comment 21

[:gerard-majax]

Jason, it seems the issue is related to the telco operating the data network, as documented in comment 19. Based on those informations, I would close this bug as INVALID.

Comment 22

[Jason Smith [:jsmith]]

Ok. If someone disagrees, feel free to reopen.

Comment 23

[Joshua Mitchell (Inactive)]

clearing my need-info