Secure webapp url fails to open using the webapp-container when the url has a self signed certificate

Asked by Wayne Lloyd on 2015-07-07

Problem: Secure webapp url fails to open using the webapp-container when the url has a self signed certificate

Application Output: [0707/223857:ERROR:cert_verify_proc_nss.cc(886)] CERT_PKIXVerifyCert for 192.168.0.253 failed err=-8172

I can open the url manually in the webbrowser-app after I accept the untrusted certificate warning

Please could someone advise if this is a bug or a feature?

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu webbrowser-app Edit question
Assignee:
No assignee Edit question
Last query:
2015-07-11
Last reply:
2015-07-11

What URL does the app open?

Wayne Lloyd (waynelloyd) said : #2

The app opens an internal server IP, I found a url that produces the same result https://www.pcwebshop.co.uk/

Certificate died in 2012.

I have the same issue in Windows 7 here.

You could contact the owners to alert them to the issue but the cert is long dead.

Wayne Lloyd (waynelloyd) said : #4

Maybe I have not described the problem well enough?

The URL I provided is an example of a URL that has an problem with its certificate I don't care about the website content, in the web-browser app a privacy error is displayed with a button allowing you to proceed to the website ignoring the invalid certificate

When a url with an invalid certificate is opened using the webapp-container it opens a blank page and does not provide a privacy error that allows users to proceed and open the website anyway

Should the webapp-container open urls with invalid certificates?

The Web servers can self sign if the loaded cert is expired.

Contacting the owner will prompt them to renew it

Can you help with this problem?

Provide an answer of your own, or ask Wayne Lloyd for more information if necessary.

To post a message you must log in.