sync-1 Reporter
	Description • 11 years ago

Mozilla build ID:20130715070218
 
 
 Created an attachment (id=474792)
 logcat
 
 DEFECT DESCRIPTION:
 
  Granting a permanent exception to a site in an app and opening that same location in the browser produces a cert error
  OR
  Granting a permanent exception to a site in the browser and opening that same location in an app should get you a cert error
 
  REPRODUCING PROCEDURES:
 
 1.Install "Hosted App Test Case 1" from http://mozqa.com/webapi-permissions-tests/ 
 
 2.Launch it and go to the link titled "WebAPI Permissions Tests" 
 
 3.Select "Unknown Cert Site" and select add permanent exception for the site within the app 
 
 4.When I visit https://cav.receita.fazenda.gov.br/eCAC/Aplicacao.aspx in the browser after visiting the Unknown Cert Site within the Test WebAPI Permissions app and providing a permanent exception-->not get a cert error-->KO
 
 
 
 OR
 1.Install "Hosted App Test Case 1" from http://mozqa.com/webapi-permissions-tests/ 
 
 2.Launch it and go to the link titled "WebAPI Permissions Tests" 
 
 3.When I visit Expired Cert Site in the Test WebAPI Permissions app after granting a permanent exception to the site in the browser at https://summitbook.mozilla.org/->not get a cert error-->KO
 
 
 
 
  EXPECTED BEHAVIOUR:
 
  Then I should get a cert error
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
  https://moztrap.mozilla.org/manage/case/6922/
  https://moztrap.mozilla.org/manage/case/6925/
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
  mid
  REPRODUCING RATE:
  5/5
  For FT PR, Please list reference mobile's behavior:

	sync-1 Reporter
	Comment 1 • 11 years ago

Clone from brother

	Andrew Overholt [:overholt]
	Comment 3 • 11 years ago

Is this behaviour different from v1.0.1?  I imagine that we're storing the exceptions in an app-specific location and not global to the device.

	Viga
	Comment 4 • 11 years ago

It can be reproduced on v1.0.1


 visit in browser: prompts "the address isn't valid"
    visit in Hosted App Test Case 1:prompts"The webapi permissions is not
loading properly"

	Jason Smith [:jsmith]
	Comment 5 • 11 years ago

Already got a bug on this, non-blocker.

	Jason Smith [:jsmith]
	Comment 6 • 11 years ago

The reasoning for this is that when we grant a certificate exception, it's granted to the chrome process. We would need to implement per app cert handling, which was deemed a non-blocker for 1.1 (which is what bug 858730 would fix).