Bug 558912 – dev-libs/nss causes error on second https request

• Product: Gentoo Linux
• Status: RESOLVED OBSOLETE

[Description Tiago Batista 2015-08-27 12:40:00 UTC]

The bug and solution are posted at https://bugzilla.redhat.com/show_bug.cgi?id=1241172

I have confirmed the same behaviour on my systems, and so far the proposed patch does fix the issue without causing additional problems that I could detect.

So far I only experienced this issue on my owncloud install, but given the wide usage of nss, its likely that other programs are being affected as well.

Reproducible: Always

Steps to Reproduce:
1. curl -v -I https://owncloud.org/ https://www.owncloud.org/

Actual Results:  
The second request fails with a 400 error code

Expected Results:  
The expected return for the second request is a 301

[Comment 1 Lars Wendler (Polynomial-C) (RETIRED) 2015-08-27 12:57:07 UTC]

This is not even fixed in upstream's current nss hg repository which makes me think that upsteam might not be aware of this bug/fix.

[Comment 2 Tiago Batista 2015-08-27 13:09:54 UTC]

I found that from the corresponding owncloud discussion at https://github.com/owncloud/core/issues/16255, but that discussion is not pertinent to this bug.

As for the upstream, if they are not aware then now is a good time as any to make them aware, should I raise the issue, or should I let the gentoo package manager raise it upstream? I do not think I have the competence to discuss the issue with the nss team as I do not know the codebase at all.

[Comment 3 Ian Stakenvicius (RETIRED) 2015-08-27 16:59:20 UTC]

(In reply to Tiago Batista from comment #2)
> I found that from the corresponding owncloud discussion at
> https://github.com/owncloud/core/issues/16255, but that discussion is not
> pertinent to this bug.
> 
> As for the upstream, if they are not aware then now is a good time as any to
> make them aware, should I raise the issue, or should I let the gentoo
> package manager raise it upstream? I do not think I have the competence to
> discuss the issue with the nss team as I do not know the codebase at all.

If you could file the bug upstream that would be appreciated.  Don't worry about not knowing the codebase, that's their job; they will want to know details of the failure though and you're likely best to answer those questions.

[Comment 4 Jory A. Pratt 2015-11-27 02:33:15 UTC]

It appears that curl has addressed the issue already with 7.45.0 I am in agreement with upstream that this is not an appropriate fix for nss.

[Comment 5 Jory A. Pratt 2017-08-26 17:56:05 UTC]

If you feel I have closed your bug and it is still a current issue, please reopen and update it completely. We will not work bugs that have no ebuild in tree any longer or can not be reproduced with a current system.

Thank You for your support and understanding
The Mozilla Team