1031366 - sec_error_ocsp_malformed_response with https://www.feedly.com

Status: RESOLVED DUPLICATE of bug 1031022

(Core :: Security: PSM, defect)

Description

[Paul Black]

Build id: 20140627030212

Go to https://www.feedly.com
I get:

Secure Connection Failed

An error occurred during a connection to www.feedly.com. The response from the OCSP server was corrupted or improperly formed. (Error code: sec_error_ocsp_malformed_response)

    The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
    Please contact the website owners to inform them of this problem.


Obviously, I expect the page to load. Page works in Konqueror.

Comment 1

[Alice0775 White]

Regression window(m-i)
Good
https://hg.mozilla.org/integration/mozilla-inbound/rev/11ce0e5823f4
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0 ID:20140625214603
Bad:
https://hg.mozilla.org/integration/mozilla-inbound/rev/904975e569b5
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0 ID:20140625221107
Pushlog:
http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=11ce0e5823f4&tochange=904975e569b5


In local build
Last Good: 93bc682527b4
First Bad: bfd435db3f9e

Regressed by:
bfd435db3f9e	Brian Smith — Bug 1029364: Centralize version parsing in BackCert::Init, r=cviecco

Blocks: 1029364

Comment 2

[Brian Smith (:briansmith, :bsmith, use NEEDINFO?)]

Thanks for the report and regression range finding.

Please include the "sec_error_" error name (in this case, sec_error_ocsp_malformed_response) in the bug report and in the summary when you get a certificate error like this.

Comment 3

[Brian Smith (:briansmith, :bsmith, use NEEDINFO?)]

(In reply to Brian Smith (:briansmith, was :bsmith; NEEDINFO? for response) from comment #2)
> Thanks for the report and regression range finding.
> 
> Please include the "sec_error_" error name (in this case,
> sec_error_ocsp_malformed_response) in the bug report and in the summary when
> you get a certificate error like this.

Oh, you did do so on this bug! Perfect! Thank you!